-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-121621: Use PyMutex for writes to asyncio state #121622
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
Conversation
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 mutex locking should be limited to the free-threaded build. You can define some macros that that lock the mutex, but are are no-ops if Py_GIL_DISABLED
is not defined.
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.
LGTM, with one minor comment. It'd be good to get @kumaraditya303's feedback as well.
Thanks @kumaraditya303 for the reviews! |
Thanks @Fidget-Spinner for the PR, and @kumaraditya303 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, @Fidget-Spinner and @kumaraditya303, I could not cleanly backport this to
|
…onGH-121622) (cherry picked from commit 5d6861a) Co-authored-by: Ken Jin <[email protected]> Co-authored-by: Kumar Aditya <[email protected]>
GH-121774 is a backport of this pull request to the 3.13 branch. |
…#121774) (cherry picked from commit 5d6861a) Co-authored-by: Ken Jin <[email protected]> Co-authored-by: Kumar Aditya <[email protected]>
Co-authored-by: Kumar Aditya <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.