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.
gh-126907: Lock the
atexit
state on the free-threaded build #126908New 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
gh-126907: Lock the
atexit
state on the free-threaded build #126908Changes from all commits
b8e4ae8
d54bca9
0601a6d
2fcee90
9eeea2e
60bb43f
fd8a0df
cca1bd5
e4ce835
d1acb86
801c4f1
a48f2ac
9688361
826dbe3
48c1b11
a2d4afa
5cc26fe
32e7415
11f7e16
9a8edf9
f4beed7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The explicit unlocking means that this still has re-entrancy and concurrency issues if the callback list is modified during the comparison.
callbacks[i]
may be a different callback.Using critical sections doesn't completely avoid the problem if
__eq__
is particularly weird, but it avoids it for the common case of identity comparison and the issues are limited to the cases where the GIL-enabled build has issues as well.