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

pitrou · pitrou · commit 9bd3bbcfe8f4 · 2011-03-13T23:28:28.000+01:00
diff --git a/Doc/ACKS.txt b/Doc/ACKS.txt
@@ -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
diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst
@@ -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
 
