mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-11-08 21:52:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Replace example with simpler alternative using PyGILState_{Ensure,Require). Can someone please confirm this change is OK?

Browse source
This commit is contained in:
Andrew M. Kuchling 2004-07-10 13:42:52 +00:00
parent 371d98ab15
commit ff8113f8d0
1 changed files with 5 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

18
Doc/api/init.tex
View file

@ -470,23 +470,15 @@ Assuming you have access to an interpreter object, the typical idiom
for calling into Python from a C thread is for calling into Python from a C thread is
\begin{verbatim} \begin{verbatim}
PyThreadState *tstate; PyGILState_STATE gstate;
PyObject *result; gstate = PyGILState_Ensure();
/* interp is your reference to an interpreter object. */
tstate = PyThreadState_New(interp);
PyEval_AcquireThread(tstate);
/* Perform Python actions here. */ /* Perform Python actions here. */
result = CallSomeFunction(); result = CallSomeFunction();
/* evaluate result */ /* evaluate result */
/* Release the thread. No Python API allowed beyond this point. */ /* Release the thread. No Python API allowed beyond this point. */
PyEval_ReleaseThread(tstate); PyGILState_Release(gstate);
/* You can either delete the thread state, or save it
until you need it the next time. */
PyThreadState_Delete(tstate);
\end{verbatim} \end{verbatim}
\begin{ctypedesc}{PyInterpreterState} \begin{ctypedesc}{PyInterpreterState}
@ -727,8 +719,8 @@ Failure is a fatal error.
\begin{cfuncdesc}{void}{PyGILState_Release}{PyGILState_STATE} \begin{cfuncdesc}{void}{PyGILState_Release}{PyGILState_STATE}
Release any resources previously acquired. After this call, Python's Release any resources previously acquired. After this call, Python's
state will be the same as it was prior to the corresponding state will be the same as it was prior to the corresponding
\cfunction{PyGILState_Ensure} call (but generally this state will be unknown to \cfunction{PyGILState_Ensure} call (but generally this state will be
the caller, hence the use of the GILState API.) unknown to the caller, hence the use of the GILState API.)
Every call to \cfunction{PyGILState_Ensure()} must be matched by a call to Every call to \cfunction{PyGILState_Ensure()} must be matched by a call to
\cfunction{PyGILState_Release()} on the same thread. \cfunction{PyGILState_Release()} on the same thread.