Mercurial > cpython-lru_cache-weakref
diff Doc/api/init.tex @ 32574:228323895271 legacy-trunk
Replace example with simpler alternative using PyGILState_{Ensure,Require). Can someone please confirm this change is OK?
| author | Andrew M. Kuchling <amk@amk.ca> |
|---|---|
| date | Sat, 10 Jul 2004 13:42:52 +0000 |
| parents | 153c517bc6e9 |
| children | 511ffc62b298 |
line wrap: on
line diff
--- a/Doc/api/init.tex Sat Jul 10 13:31:18 2004 +0000 +++ b/Doc/api/init.tex Sat Jul 10 13:42:52 2004 +0000 @@ -470,23 +470,15 @@ for calling into Python from a C thread is \begin{verbatim} - PyThreadState *tstate; - PyObject *result; - - /* interp is your reference to an interpreter object. */ - tstate = PyThreadState_New(interp); - PyEval_AcquireThread(tstate); + PyGILState_STATE gstate; + gstate = PyGILState_Ensure(); /* Perform Python actions here. */ result = CallSomeFunction(); /* evaluate result */ /* Release the thread. No Python API allowed beyond this point. */ - PyEval_ReleaseThread(tstate); - - /* You can either delete the thread state, or save it - until you need it the next time. */ - PyThreadState_Delete(tstate); + PyGILState_Release(gstate); \end{verbatim} \begin{ctypedesc}{PyInterpreterState} @@ -727,8 +719,8 @@ \begin{cfuncdesc}{void}{PyGILState_Release}{PyGILState_STATE} Release any resources previously acquired. After this call, Python's state will be the same as it was prior to the corresponding -\cfunction{PyGILState_Ensure} call (but generally this state will be unknown to -the caller, hence the use of the GILState API.) +\cfunction{PyGILState_Ensure} call (but generally this state will be +unknown to the caller, hence the use of the GILState API.) Every call to \cfunction{PyGILState_Ensure()} must be matched by a call to \cfunction{PyGILState_Release()} on the same thread.
