mirror of
https://github.com/python/cpython.git
synced 2025-08-04 08:59:19 +00:00
New PyGILState_ API - implements pep 311, from patch 684256.
This commit is contained in:
parent
e36b690087
commit
8d98d2cb95
10 changed files with 395 additions and 131 deletions
|
@ -72,6 +72,7 @@ typedef struct _ts {
|
|||
PyObject *dict;
|
||||
|
||||
int tick_counter;
|
||||
int gilstate_counter;
|
||||
|
||||
/* XXX signal handlers should also be here */
|
||||
|
||||
|
@ -104,6 +105,51 @@ PyAPI_DATA(PyThreadState *) _PyThreadState_Current;
|
|||
#define PyThreadState_GET() (_PyThreadState_Current)
|
||||
#endif
|
||||
|
||||
typedef
|
||||
enum {PyGILState_LOCKED, PyGILState_UNLOCKED}
|
||||
PyGILState_STATE;
|
||||
|
||||
/* Ensure that the current thread is ready to call the Python
|
||||
C API, regardless of the current state of Python, or of its
|
||||
thread lock. This may be called as many times as desired
|
||||
by a thread so long as each call is matched with a call to
|
||||
PyGILState_Release(). In general, other thread-state APIs may
|
||||
be used between _Ensure() and _Release() calls, so long as the
|
||||
thread-state is restored to its previous state before the Release().
|
||||
For example, normal use of the Py_BEGIN_ALLOW_THREADS/
|
||||
Py_END_ALLOW_THREADS macros are acceptable.
|
||||
|
||||
The return value is an opaque "handle" to the thread state when
|
||||
PyGILState_Acquire() was called, and must be passed to
|
||||
PyGILState_Release() to ensure Python is left in the same state. Even
|
||||
though recursive calls are allowed, these handles can *not* be shared -
|
||||
each unique call to PyGILState_Ensure must save the handle for its
|
||||
call to PyGILState_Release.
|
||||
|
||||
When the function returns, the current thread will hold the GIL.
|
||||
|
||||
Failure is a fatal error.
|
||||
*/
|
||||
PyAPI_FUNC(PyGILState_STATE) PyGILState_Ensure(void);
|
||||
|
||||
/* Release any resources previously acquired. After this call, Python's
|
||||
state will be the same as it was prior to the corresponding
|
||||
PyGILState_Acquire call (but generally this state will be unknown to
|
||||
the caller, hence the use of the GILState API.)
|
||||
|
||||
Every call to PyGILState_Ensure must be matched by a call to
|
||||
PyGILState_Release on the same thread.
|
||||
*/
|
||||
PyAPI_FUNC(void) PyGILState_Release(PyGILState_STATE);
|
||||
|
||||
/* Helper/diagnostic function - get the current thread state for
|
||||
this thread. May return NULL if no GILState API has been used
|
||||
on the current thread. Note the main thread always has such a
|
||||
thread-state, even if no auto-thread-state call has been made
|
||||
on the main thread.
|
||||
*/
|
||||
PyAPI_FUNC(PyThreadState *) PyGILState_GetThisThreadState(void);
|
||||
|
||||
/* Routines for advanced debuggers, requested by David Beazley.
|
||||
Don't use unless you know what you are doing! */
|
||||
PyAPI_FUNC(PyInterpreterState *) PyInterpreterState_Head(void);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue