Stowage/cpython
2
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-10-30 21:21:22 +00:00
Code Issues Projects Releases Packages Wiki Activity

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

Browse source
This commit is contained in:
Antoine Pitrou 2011-03-13 23:28:28 +01:00
parent 34db469895
commit 9bd3bbcfe8
2 changed files with 3 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

1
Doc/ACKS.txt
View file

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

6
Doc/c-api/init.rst
View file

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