From: kobarity <kobarity@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Keglo Stephane <stephanekeglo@gmail.com>
Cc: 74894@debbugs.gnu.org
Subject: bug#74894: 29.4; Emacs not responding when calling python-fix-imports
Date: Sat, 04 Jan 2025 23:17:29 +0900 [thread overview]
Message-ID: <eke78qrqwtmu.wl-kobarity@gmail.com> (raw)
In-Reply-To: <86frlyer87.fsf@gnu.org> <eke7ed1z9266.wl-kobarity@gmail.com> <eke7frmg8qd6.wl-kobarity@gmail.com>
Eli Zaretskii wrote:
>
> [Please use Reply All, to have everyone CC'ed.]
>
> > Date: Sun, 22 Dec 2024 14:35:51 +0000
> > From: Keglo Stephane <stephanekeglo@gmail.com>
> >
> > This is a simple recipe to reproduce the bug:
> > 1- open an empty python buffer
> > 2- start an inferior python shell C-c C-p
> > 3- Enter the following code: print(string.digits)
> > 4- Evaluation of this code should throw an exception since the string module is not imported
> > 5- Trying to use python-add-import ( C-c TAB a) or python-fix-imports ( C-c TAB fix) to add the missing
> > import, Emacs freeze a moment.
> > you have to press Ctrl-G to make Emacs respond again.
>
> kobarity, any suggestions?
Sorry, I did not realize that email was a DM. Here is my reply:
> Thank you, but I cannot reproduce the problem.
>
> Import management depends on the contents of the directory (or more
> precisely, the project). If you try the above procedure with an empty
> directory (outside of a project, such as a Git repository), you may
> not have problems. Therefore, it may be a little difficult to
> establish a reproducible recipe.
>
> Just to add, import management works without inferior python.
So, my expectation is that Keglo will do the research I previously
mailed:
> While Emacs is not responding, run "top" to see if there is a process
> with high CPU utilization. It is likely Python or Emacs is using CPU.
> If the CPU utilization of Python is high, please tell us the arguments
> of the Python process. If the CPU utilization of Emacs is high,
> please check if you can abort with Ctrl-G or sending SIGUSR2 signal.
> If you can abort, please send the backtrace:
>
> 1. emacs -Q
> 2. M-x load-fie
> Specify the location of python.el (or python.el.gz, not
> python.elc). You can use M-x locate-library and enter "python" to
> locate the file.
> 3. M-x toggle-debug-on-quit
> 4. Reproduce the issue.
> 5. Abort with Ctrl-G or SIGUSR2.
Other useful information includes:
- Whether you are working on "project"
- Whether or not the "freeze" last for a few minutes or so
next prev parent reply other threads:[~2025-01-04 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 2:52 bug#74894: 29.4; Emacs not responding when calling python-fix-imports Keglo Stephane
2024-12-21 10:39 ` Eli Zaretskii
2024-12-21 15:16 ` kobarity
2024-12-21 16:12 ` Eli Zaretskii
2024-12-22 1:21 ` kobarity
2025-01-04 14:17 ` kobarity [this message]
[not found] ` <message from kobarity on Sun, 22 Dec 2024 00:16:53 +0900>
[not found] ` <RJGWOS.GMP8CE1OML6U1@gmail.com>
2025-01-04 11:46 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eke78qrqwtmu.wl-kobarity@gmail.com \
--to=kobarity@gmail.com \
--cc=74894@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stephanekeglo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).