Searched refs:PyEval_ReleaseLock (Results 1 – 16 of 16) sorted by relevance
125 PyAPI_FUNC(void) PyEval_ReleaseLock(void);
186 PyAPI_FUNC(void) PyEval_ReleaseLock(void);
338 PyEval_ReleaseLock(); in run_interpreter()
167 PyEval_ReleaseLock
321 PyEval_ReleaseLock(); in PyThreadState_DeleteCurrent()
265 PyEval_ReleaseLock(void) in PyEval_ReleaseLock() function
179 PyEval_ReleaseLock=python36.PyEval_ReleaseLock
20 single: PyEval_ReleaseLock()35 :c:func:`PyEval_ReleaseLock`, and :c:func:`PyEval_AcquireLock`. This initializes518 single: PyEval_ReleaseLock()525 operations such as :c:func:`PyEval_ReleaseLock` or798 .. c:function:: void PyEval_ReleaseLock()
466 PyEval_ReleaseLock(); in PyThreadState_DeleteCurrent()
257 PyEval_ReleaseLock(void) in PyEval_ReleaseLock() function
855 "PyEval_ReleaseLock"
368 PyEval_ReleaseLock:void:::
374 PyEval_ReleaseLock:void:::
879 .. c:function:: void PyEval_ReleaseLock()
2724 :c:func:`PyEval_ReleaseLock()` have been officially deprecated. The
10998 PyEval_ReleaseLock(). The thread-state aware APIs should be used instead.