Roundup Robot devnull@devnull 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
Antoine Pitrou pit...@free.fr added the comment:
Patch now committed, thank you!
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11329
Gediminas Liktaras glikta...@gmail.com 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
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11329
___
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
Can you write a patch for the documentation?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11329
___
New submission from Juraj Ivancic juraj.ivan...@gmail.com:
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
Antoine Pitrou pit...@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().
