[issue11329] PyEval_InitThreads() not safe before Py_Initialize()

Antoine Pitrou added the comment: Patch now committed, thank you! -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue11329] PyEval_InitThreads() not safe before Py_Initialize()

Roundup Robot added the comment: New changeset 4c59cd84086f by Antoine Pitrou in branch '3.2': Issue #11329: PyEval_InitThreads() cannot be called before Py_Initialize() anymore http://hg.python.org/cpython/rev/4c59cd84086f New changeset 3c0edb157ea2 by Antoine Pitrou in branch 'default': Issu

[issue11329] PyEval_InitThreads() not safe before Py_Initialize()

Gediminas Liktaras added the comment: I have attached a patch that fixes this issue. Please let me know if there are any problems. -- keywords: +patch nosy: +gliktaras Added file: http://bugs.python.org/file21094/issue11329-1.patch ___ Python tracke

[issue11329] PyEval_InitThreads() not safe before Py_Initialize()

STINNER Victor added the comment: Can you write a patch for the documentation? -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue11329] PyEval_InitThreads() not safe before Py_Initialize()

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue11329] PyEval_InitThreads() not safe before Py_Initialize()

Antoine Pitrou added the comment: Given the way the new GIL works, I'm afraid it's not really possible to support this (it needs some thread-state to be available). Note that there is no reason, AFAIK, why you would want to call PyEval_InitThreads() before Py_Initialize(). -- assignee

[issue11329] PyEval_InitThreads() not safe before Py_Initialize()

New submission from Juraj Ivancic : It seems that PyEval_InitThreads() can no longer be called before Py_Initialize(). I get a fatal error in PyThreadState_GET(). This contradicts the documentation http://docs.python.org/release/3.2/c-api/init.html#PyEval_InitThreads Minimal repro: #include "P