Clarify that the Python interpreter lock need *not* be held by

gvanrossum · gvanrossum · commit ed9dcc10f879 · 1998-08-07T18:28:03.000Z
PyInterpreterState_New() and PyThreadState_New() -- but that you may
use it to serialize calls to them.
diff --git a/Doc/api/api.tex b/Doc/api/api.tex
@@ -2914,8 +2914,9 @@ \section{Thread State and the Global Interpreter Lock}
 interpreter lock has been created.
 
 \begin{cfuncdesc}{PyInterpreterState*}{PyInterpreterState_New}{}
-Create a new interpreter state object.  The interpreter lock must be
-held.
+Create a new interpreter state object.  The interpreter lock need not
+be held, but may be held if it is necessary to serialize calls to this
+function.
 \end{cfuncdesc}
 
 \begin{cfuncdesc}{void}{PyInterpreterState_Clear}{PyInterpreterState *interp}
@@ -2931,7 +2932,8 @@ \section{Thread State and the Global Interpreter Lock}
 
 \begin{cfuncdesc}{PyThreadState*}{PyThreadState_New}{PyInterpreterState *interp}
 Create a new thread state object belonging to the given interpreter
-object.  The interpreter lock must be held.
+object.  The interpreter lock need not be held, but may be held if it
+is necessary to serialize calls to this function.
 \end{cfuncdesc}
 
 \begin{cfuncdesc}{void}{PyThreadState_Clear}{PyThreadState *tstate}
