-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Revert "gh-115432: Add critical section variant that handles a NULL object (#115433)" #118861
Conversation
…NULL object (python#115433)" This reverts commit ad4f909. The API ended up not being used.
@Yhg1s - this isn't really a bug fix, but it's definitely not a feature. Would it be appropriate to backport this revert to 3.13? |
9f8175b
to
49a359e
Compare
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!
Yeah, backporting it to 3.13 is fine until we get to rc1. |
Thanks @colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…NULL object (pythonGH-115433)" (pythonGH-118861) This reverts commit ad4f909. The API ended up not being used. (cherry picked from commit 46c8081) Co-authored-by: Sam Gross <[email protected]>
GH-118872 is a backport of this pull request to the 3.13 branch. |
…NULL object (python#115433)" (python#118861) This reverts commit ad4f909. The API ended up not being used.
This reverts commit ad4f909.
This internal API ended up not being used.
Py_BEGIN_CRITICAL_SECTION
that accepts aNULL
argument #115432