A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] PyEval_InitThreads() no longer safe before Py_Initialize() in 3.2 [Python-Dev] PyEval_InitThreads() no longer safe before Py_Initialize() in 3.2Juraj Ivančić juraj.ivancic at gmail.com
Fri Feb 25 09:48:54 CET 2011
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;
}

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4