[3.6] bpo-20891: Py_Initialize() now creates the GIL (#4700) - #5421
[3.6] bpo-20891: Py_Initialize() now creates the GIL (#4700)#5421vstinner wants to merge 1 commit into
Conversation
Sorry, something went wrong.
|
@pitrou: Do you think that it's ok to make such change in the stable 3.6? IMHO it's a bugfix and so must be backported to 3.6. |
Sorry, something went wrong.
|
@vstinner I don't think so. People can already call PyEval_InitThreads. |
Sorry, something went wrong.
Since only two users complained about https://bugs.python.org/issue20891 in 3 years, I agree that it's ok to not fix Python 2.7 and 3.6. The workaround is to call PyEval_InitThreads() before starting the first thread. I wasn't excited to make such stable in stable 2.7 and 3.6 anyway :-) |
Sorry, something went wrong.
The GIL is no longer created "on demand" to fix a race condition when
PyGILState_Ensure() is called in a non-Python thread.
Reenable test_capi.test_bpo20891().
(cherry picked from commit 2914bb3)
https://bugs.python.org/issue20891