tf: account for Python GIL explicit initialization deprecation from Python 3.7 to 3.9 #1909
Conversation
This file contains 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
…ython 3.7 to 3.9 Starting with Python 3.7, the GIL is initialized as part of Py_Initialize() and PyEval_InitThreads() no longer needs to be called separately. In Python 3.9, PyEval_InitThreads() no longer does anything and was marked deprecated. See here for more detail: https://docs.python.org/3/c-api/init.html#c.PyEval_InitThreads This change avoids the use of PyEval_InitThreads() and PyEval_ThreadsInitialized() when building against Python 3.7 or later.
|
Filed as internal issue #USD-7439 |
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.
Description of Change(s)
Starting with Python 3.7, the GIL is initialized as part of Py_Initialize() and PyEval_InitThreads() no longer needs to be called separately. In Python 3.9, PyEval_InitThreads() no longer does anything and was marked deprecated.
See here for more detail:
https://docs.python.org/3/c-api/init.html#c.PyEval_InitThreads
This change avoids the use of PyEval_InitThreads() and PyEval_ThreadsInitialized() when building against Python 3.7 or later and cleans up the deprecation warnings that are otherwise issued. Those functions are slated for removal in Python 3.11.