Repository navigation
Align shutdown flush and unraisable reporting with CPython #9810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
youknowone
merged 10 commits into
RustPython:main
from
youknowone:shutdown-unraisable-reporting-20261104
Nov 12, 2026
+531
−207
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
8c6137f
Align shutdown flush and unraisable reporting with CPython
youknowdot 1395ec6
Fix shutdown CI locks and preserve input read-ahead
youknowdot ce71742
Adapt unraisable fallback to current traceback writer
codex 9b2749d
Use core RefCell for retained input reader
codex c70cb65
Mark timed mutex tests with explicit test cfg
codex 059f39f
Share interactive input read-ahead across threads
codex 290ca50
Exercise input from the result audit hook
codex f0d1a17
Drain both terminals while testing input redirection
codex f00fc6a
Report __del__ failures without an unraisable object
youknowone a0ee443
Raise FileIO read, write, and close errors without a filename
youknowone File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do not create a guard from the wrapper's boolean.
If a caller passes
|_| true,lock_internalrecords ownership without acquiring the raw mutex. The returned guard then exposes mutable data without exclusion and calls unsafeunlock()on drop. If the wrapper acquires the mutex but returns false, the raw mutex remains locked. Derive the result from a verified, exactly-once acquisition instead. As per coding guidelines, “Follow Rust best practices for error handling and memory management.”Source: Coding guidelines