From ed9dcc10f87946088bc7d71292764e3f1bcc979b Mon Sep 17 00:00:00 2001 From: Guido van Rossum Date: Fri, 7 Aug 1998 18:28:03 +0000 Subject: [PATCH] Clarify that the Python interpreter lock need *not* be held by PyInterpreterState_New() and PyThreadState_New() -- but that you may use it to serialize calls to them. --- Doc/api/api.tex | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Doc/api/api.tex b/Doc/api/api.tex index b43438dd7a..93e061c458 100644 --- a/Doc/api/api.tex +++ b/Doc/api/api.tex @@ -2914,8 +2914,9 @@ is enabled at compile time, and must be called only when the 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 @@ call to \cfunction{PyInterpreterState_Clear()}. \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} -- 2.50.1