Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
gh-98627: Add an Optional Check for Extension Module Subinterpreter Compatibility#99040
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
ericsnowcurrently merged 26 commits intopython:mainfromericsnowcurrently:interpreter-multi-interp-extensions-checkFeb 16, 2023
Merged
gh-98627: Add an Optional Check for Extension Module Subinterpreter Compatibility#99040
ericsnowcurrently merged 26 commits intopython:mainfromericsnowcurrently:interpreter-multi-interp-extensions-checkFeb 16, 2023
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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
…_MULTI_INTERP_EXTENSIONS.
93ea024 to1defec3CompareContributor
erlend-aasland commentedJan 11, 2023
FYI, converting 👇🏻 |
ericsnowcurrently added a commit that referenced this pull requestFeb 6, 2023
…ters (gh-101431)The GILState API (PEP 311) implementation from 2003 made the assumption that only one thread state would ever be used for any given OS thread, explicitly disregarding the case of subinterpreters. However, PyThreadState_Swap() still facilitated switching between subinterpreters, meaning the "current" thread state (holding the GIL), and the GILState thread state could end up out of sync, causing problems (including crashes).This change addresses the issue by keeping the two in sync in PyThreadState_Swap(). I verified the fix againstgh-99040.Note that the other GILState-subinterpreter incompatibility (with autoInterpreterState) is not resolved here.#59956
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
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.
Uh oh!
There was an error while loading.Please reload this page.
Enforcing (optionally) the restriction set by PEP 489 makes sense. Furthermore, this sets the stage for a potential restriction related to a per-interpreter GIL.
This change includes the following:
_PyInterpreterConfig.check_multi_interp_extensionsPy_RTFLAGS_MULTI_INTERP_EXTENSIONS_PyImport_CheckSubinterpIncompatibleExtensionAllowed()