summaryrefslogtreecommitdiffstats
path: root/Doc/c-api/init.rst
diff options
context:
space:
mode:
authorVictor Stinner <vstinner@python.org>2020-02-01 01:30:25 (GMT)
committerGitHub <noreply@github.com>2020-02-01 01:30:25 (GMT)
commit4d96b4635aeff1b8ad41d41422ce808ce0b971c8 (patch)
tree841398922264fff5b99548bee68ff70884554040 /Doc/c-api/init.rst
parent7dc140126e918cc7c6e65aea321b7255f0020798 (diff)
downloadcpython-4d96b4635aeff1b8ad41d41422ce808ce0b971c8.zip
cpython-4d96b4635aeff1b8ad41d41422ce808ce0b971c8.tar.gz
cpython-4d96b4635aeff1b8ad41d41422ce808ce0b971c8.tar.bz2
bpo-39511: PyThreadState_Clear() calls on_delete (GH-18296)
PyThreadState.on_delete is a callback used to notify Python when a thread completes. _thread._set_sentinel() function creates a lock which is released when the thread completes. It sets on_delete callback to the internal release_sentinel() function. This lock is known as Threading._tstate_lock in the threading module. The release_sentinel() function uses the Python C API. The problem is that on_delete is called late in the Python finalization, when the C API is no longer fully working. The PyThreadState_Clear() function now calls the PyThreadState.on_delete callback. Previously, that happened in PyThreadState_Delete(). The release_sentinel() function is now called when the C API is still fully working.
Diffstat (limited to 'Doc/c-api/init.rst')
-rw-r--r--Doc/c-api/init.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst
index 7ea48ae..14049ee 100644
--- a/Doc/c-api/init.rst
+++ b/Doc/c-api/init.rst
@@ -1048,6 +1048,10 @@ All of the following functions must be called after :c:func:`Py_Initialize`.
Reset all information in a thread state object. The global interpreter lock
must be held.
+ .. versionchanged:: 3.9
+ This function now calls the :c:member:`PyThreadState.on_delete` callback.
+ Previously, that happened in :c:func:`PyThreadState_Delete`.
+
.. c:function:: void PyThreadState_Delete(PyThreadState *tstate)