Reset GIL thread static data when disposing an environment#385
Draft
gabrielgt wants to merge 2 commits intotonybaloney:mainfrom
Draft
Reset GIL thread static data when disposing an environment#385gabrielgt wants to merge 2 commits intotonybaloney:mainfrom
gabrielgt wants to merge 2 commits intotonybaloney:mainfrom
Conversation
c3d4bfc to
dfda486
Compare
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
Sign up for free
to 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.
To allow using multiple Python environments sequentially, it is necessary to completely reset the internal data of the GIL class when an environment is disposed and the Python interpreter is finalized. Otherwise, an exception will be raised when trying to access a thread state that no longer exists.
This fix doesn't fully resolve the issue #296, but it at least allows sequential execution of multiple different environments.