-
-
Notifications
You must be signed in to change notification settings - Fork 32k
gh-126986: Drop _PyInterpreterState_FailIfNotRunning() #126988
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
gh-126986: Drop _PyInterpreterState_FailIfNotRunning() #126988
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.
I noticed this problem when working on some of the other issues, but it seems to not really occur in CI for whatever reason, so I don't think there's any point in trying to test for this. LGTM.
Thanks @ericsnowcurrently for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…h-126988) We replace it with _PyErr_SetInterpreterAlreadyRunning(). (cherry picked from commit d6b3e78) Co-authored-by: Eric Snow <[email protected]>
GH-126995 is a backport of this pull request to the 3.13 branch. |
While this is a private API change, it's still technically breaking the ABI because of the |
It's okay. I'll sort out the ABI change. It's all internal ABI so we're safe to do it. |
…h-126988) We replace it with _PyErr_SetInterpreterAlreadyRunning().
…h-127112) This is a pseudo-backport of d6b3e78 (gh-126988). In that change for 3.14+, we dropped _PyInterpreterState_FailIfNotRunning() and added _PyErr_SetInterpreterAlreadyRunning(). Here, we replace usage of _PyInterpreterState_FailIfNotRunning() with the inlined equivalent of _PyErr_SetInterpreterAlreadyRunning(), without adding that function. That way we avoid changing the 3.13 ABI.
…h-126988) We replace it with _PyErr_SetInterpreterAlreadyRunning().
We replace it with
_PyErr_SetInterpreterAlreadyRunning()
.