Issue #1778: PyGILState_Ensure should not deadlock if GIL already held (pypy/pypy)

May 26, 2014
4:19 a.m.
New issue 1778: PyGILState_Ensure should not deadlock if GIL already held https://bitbucket.org/pypy/pypy/issue/1778/pygilstate_ensure-should-not-dead... Nick Williams: PyGILState_Ensure is documented as "(ensuring) that the current thread is ready to call the Python C API regardless of the current state of Python, or of the global interpreter lock". However, in PyPy, code which calls PyGILState_Ensure while already holding the GIL will deadlock. This does not happen in CPython and does not seem consistent with the Python documentation.
3950
Age (days ago)
3950
Last active (days ago)
0 comments
1 participants
participants (1)
-
Nick Williams