Issue #11329: PyEval_InitThreads() cannot be called before Py_Initialize() anymore
diff --git a/Doc/ACKS.txt b/Doc/ACKS.txt
index c51d211..7f67d36 100644
--- a/Doc/ACKS.txt
+++ b/Doc/ACKS.txt
@@ -120,6 +120,7 @@
* 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
index da55ab0..2641c8b 100644
--- a/Doc/c-api/init.rst
+++ b/Doc/c-api/init.rst
@@ -29,8 +29,7 @@
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 @@
.. 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