| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Remove PyEval_InitThreads() and PyEval_ThreadsInitialized() functions. The GIL is created by Py_Initialize() since Python 3.7, and so calling explicitly PyEval_InitThreads() was useless since Python 3.7. Deprecated in 3.9, PyEval_InitThreads() did nothing and PyEval_ThreadsInitialized() already returned true.
|
cc @encukou: FYI this PR removes a function from the stable ABI. It was deprecated for 2 Python releases. |
Sorry, something went wrong.
|
Please do not remove functions from the stable ABI. They can be removed from the API (i.e. headers), but should stay in the stable ABI. It is OK if they do nothing. |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
Oh. I didn't notice that. I close my PR and its associated issue. I'm not interested to attempt to only remove it from the API (header files). |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Remove PyEval_InitThreads() and PyEval_ThreadsInitialized()
functions. The GIL is created by Py_Initialize() since Python 3.7,
and so calling explicitly PyEval_InitThreads() was useless since
Python 3.7. Deprecated in 3.9, PyEval_InitThreads() did nothing and
PyEval_ThreadsInitialized() already returned true.
https://bugs.python.org/issue44117