[New-bugs-announce] [issue11329] PyEval_InitThreads() not safe before Py_Initialize()

Juraj Ivancic report at bugs.python.org
Sat Feb 26 10:50:07 CET 2011


New submission from Juraj Ivancic <juraj.ivancic at 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

Minimal repro:

#include "Python.h"
int main()
{
     PyEval_InitThreads();
     return 0;
}

Everything works if Py_Initialize() is called first.

----------
components: Interpreter Core
messages: 129515
nosy: Juraj.Ivancic
priority: normal
severity: normal
status: open
title: PyEval_InitThreads() not safe before Py_Initialize()
type: crash
versions: Python 3.2

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue11329>
_______________________________________


More information about the New-bugs-announce mailing list