Issue #11329: PyEval_InitThreads() cannot be called before Py_Initialize() anymore

This commit is contained in:
Antoine Pitrou 2011-03-13 23:29:10 +01:00
commit 0cfc23762f
2 changed files with 3 additions and 4 deletions

View File

@ -120,6 +120,7 @@ docs@python.org), and we'll be glad to correct the problem.
* Robert Lehmann * Robert Lehmann
* Marc-André Lemburg * Marc-André Lemburg
* Ross Light * Ross Light
* Gediminas Liktaras
* Ulf A. Lindgren * Ulf A. Lindgren
* Everett Lipman * Everett Lipman
* Mirko Liss * Mirko Liss

View File

@ -29,8 +29,7 @@ Initializing and finalizing the interpreter
Initialize the Python interpreter. In an application embedding Python, this Initialize the Python interpreter. In an application embedding Python, this
should be called before using any other Python/C API functions; with the should be called before using any other Python/C API functions; with the
exception of :c:func:`Py_SetProgramName`, :c:func:`Py_SetPath`, exception of :c:func:`Py_SetProgramName` and :c:func:`Py_SetPath`. This initializes
and :c:func:`PyEval_InitThreads`. This initializes
the table of loaded modules (``sys.modules``), and creates the fundamental the table of loaded modules (``sys.modules``), and creates the fundamental
modules :mod:`builtins`, :mod:`__main__` and :mod:`sys`. It also initializes modules :mod:`builtins`, :mod:`__main__` and :mod:`sys`. It also initializes
the module search path (``sys.path``). It does not set ``sys.argv``; use the module search path (``sys.path``). It does not set ``sys.argv``; use
@ -540,8 +539,7 @@ code, or when embedding the Python interpreter:
.. index:: single: Py_Initialize() .. index:: single: Py_Initialize()
This is a no-op when called for a second time. It is safe to call this function This is a no-op when called for a second time.
before calling :c:func:`Py_Initialize`.
.. index:: module: _thread .. index:: module: _thread