Browse Source
bpo-36475: Finalize PyEval_AcquireLock() and PyEval_AcquireThread() properly (GH-12667)
bpo-36475: Finalize PyEval_AcquireLock() and PyEval_AcquireThread() properly (GH-12667)
PyEval_AcquireLock() and PyEval_AcquireThread() now terminate the current thread if called while the interpreter is finalizing, making them consistent with PyEval_RestoreThread(), Py_END_ALLOW_THREADS, and PyGILState_Ensure().pull/12453/head
committed by
Victor Stinner
4 changed files with 51 additions and 12 deletions
-
24Doc/c-api/init.rst
-
7Doc/whatsnew/3.8.rst
-
4Misc/NEWS.d/next/Core and Builtins/2019-04-02-20-02-22.bpo-36475.CjRps3.rst
-
28Python/ceval.c
@ -0,0 +1,4 @@ |
|||
:c:func:`PyEval_AcquireLock` and :c:func:`PyEval_AcquireThread` now |
|||
terminate the current thread if called while the interpreter is |
|||
finalizing, making them consistent with :c:func:`PyEval_RestoreThread`, |
|||
:c:func:`Py_END_ALLOW_THREADS`, and :c:func:`PyGILState_Ensure`. |
|||
Write
Preview
Loading…
Cancel
Save
Reference in new issue