RetroSearch Browse

Sat Feb 26 10:53:00 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-February/108331.html

On 26.2.2011 10:28, Eric Smith wrote:
> On 2/25/2011 3:48 AM, Juraj Ivančić wrote:
>> 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;
>> }
>
> Can you open an issue in the bug tracker?

http://bugs.python.org/issue11329

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-February/108331.html below:

[Python-Dev] PyEval_InitThreads() no longer safe before Py_Initialize() in 3.2