gh-82183: Do not restart the busy IDLE shell when running without restart#152745
Merged
terryjreedy merged 1 commit intoJul 1, 2026
Merged
Conversation
…ut restart "Run... Customized" with "Restart shell" unchecked restarted the shell anyway when it was busy executing code, killing any pending input. It now reports that the shell is executing and does not run.
Member
|
With the patch, the message is displayed just once instead of twice. I added a draft doc issue on the project page to maybe say something in the doc. |
|
Thanks @serhiy-storchaka for the PR, and @terryjreedy for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14, 3.15. |
|
GH-152832 is a backport of this pull request to the 3.15 branch. |
|
GH-152833 is a backport of this pull request to the 3.14 branch. |
|
GH-152834 is a backport of this pull request to the 3.13 branch. |
terryjreedy
pushed a commit
that referenced
this pull request
Jul 1, 2026
…out restart (GH-152745) (#152834) gh-82183: Do not restart the busy IDLE shell when running without restart (GH-152745) "Run... Customized" with "Restart shell" unchecked restarted the shell anyway when it was busy executing code, killing any pending input. It now reports that the shell is executing just once, not twice, and does not run. (cherry picked from commit be449b1) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
terryjreedy
pushed a commit
that referenced
this pull request
Jul 1, 2026
…out restart (GH-152745) (#152833) gh-82183: Do not restart the busy IDLE shell when running without restart (GH-152745) "Run... Customized" with "Restart shell" unchecked restarted the shell anyway when it was busy executing code, killing any pending input. It now reports that the shell is executing just once, not twice, and does not run. (cherry picked from commit be449b1) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
terryjreedy
pushed a commit
that referenced
this pull request
Jul 1, 2026
…out restart (GH-152745) (#152832) gh-82183: Do not restart the busy IDLE shell when running without restart (GH-152745) "Run... Customized" with "Restart shell" unchecked restarted the shell anyway when it was busy executing code, killing any pending input. It now reports that the shell is executing just once, not twice, and does not run. (cherry picked from commit be449b1) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
AttributeErrorin the original report (bpo-38002) was fixed by bpo-42508. This addresses the remaining problem noted by @terryjreedy: with the Shell busy executing code (e.g. blocked oninput()), using "Run... Customized" with "Restart shell" unchecked restarted the subprocess anyway.run_module_eventskips the explicitrestart_subprocesswhen restart is unchecked, butruncodethen restarts the busy shell on its own, overriding the user's choice and killing the pending input.The new code cannot run in the busy shell's namespace without restarting it, so when restart is unchecked and the shell is executing it now reports "Already executing" and aborts, instead of restarting anyway.
🤖 Generated with Claude Code