[issue26003] Issues with PyEval_InitThreads and PyGILState_Ensure

2021-01-20 Thread STINNER Victor
STINNER Victor added the comment: The GIL is now created by _PyEval_InitGIL() which is called by Py_Initialize(): at Python startup. _PyRuntime.main_thread is set by _PyRuntime_Initialize() which is also called by Py_Initialize(): at Python startup. The code to handle signals and pending

[issue26003] Issues with PyEval_InitThreads and PyGILState_Ensure

2020-12-19 Thread Irit Katriel
Irit Katriel added the comment: Since PyEval_InitThreads is now an empty function and to be removed, this issue seems out of date. A I right? -- nosy: +iritkatriel resolution: -> out of date status: open -> pending ___ Python tracker

[issue26003] Issues with PyEval_InitThreads and PyGILState_Ensure

2016-01-15 Thread SilentGhost
Changes by SilentGhost : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list

[issue26003] Issues with PyEval_InitThreads and PyGILState_Ensure

2016-01-03 Thread tzickel
New submission from tzickel: A few issues regarding threads: A. (Python 2 & 3) The documentation (https://docs.python.org/3/c-api/init.html) about initializing the GIL/Threading system does not specify that calling PyEval_InitThreads actually binds the calling thread as the main_thread in the

[issue26003] Issues with PyEval_InitThreads and PyGILState_Ensure

2016-01-03 Thread tzickel
Changes by tzickel : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing