Some function renamings were overlooked in the PEP; repair them.
This commit is contained in:
parent
abd928379d
commit
bf4a5c7ebb
|
@ -184,14 +184,14 @@ Design and Implementation
|
||||||
- remember the current state of the lock (owned/not owned)
|
- remember the current state of the lock (owned/not owned)
|
||||||
- If the current state does not own the GIL, acquire it.
|
- If the current state does not own the GIL, acquire it.
|
||||||
- Increment a counter for how many calls to
|
- Increment a counter for how many calls to
|
||||||
PyAutoThreadState_Ensure have been made on the current thread.
|
PyGILState_Ensure have been made on the current thread.
|
||||||
- return
|
- return
|
||||||
|
|
||||||
The general operation of PyAutoThreadState_Release() will be:
|
The general operation of PyGILState_Release() will be:
|
||||||
|
|
||||||
- assert our thread currently holds the lock.
|
- assert our thread currently holds the lock.
|
||||||
- If old state indicates lock was previously unlocked, release GIL.
|
- If old state indicates lock was previously unlocked, release GIL.
|
||||||
- Decrement the PyAutoThreadState_Ensure counter for the thread.
|
- Decrement the PyGILState_Ensure counter for the thread.
|
||||||
- If counter == 0:
|
- If counter == 0:
|
||||||
- release and delete the PyThreadState.
|
- release and delete the PyThreadState.
|
||||||
- forget the ThreadState as being owned by the thread.
|
- forget the ThreadState as being owned by the thread.
|
||||||
|
|
Loading…
Reference in New Issue