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

Antoine Pitrou report at bugs.python.org
Sat Feb 26 11:01:54 CET 2011

Antoine Pitrou <pitrou at free.fr> 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:  -> docs at python
components: +Documentation
nosy: +amaury.forgeotdarc, docs at python, pitrou
type: crash -> behavior
versions: +Python 3.3

Python tracker <report at bugs.python.org>

More information about the docs mailing list