Lines Matching refs:GIL

653 interpreter lock` or :term:`GIL`, that must be held by the current thread before
662 :term:`GIL` may operate on Python objects or call Python/C API functions.
677 Releasing the GIL from extension code
680 Most extension code manipulating the :term:`GIL` has the following simple
725    the GIL, but it can also be useful before calling long-running computations
728    standard :mod:`zlib` and :mod:`hashlib` modules release the GIL when
741 management), they don't hold the GIL, nor is there a thread state structure
747 creating a thread state data structure, then acquiring the GIL, and finally
750 the GIL, and finally free the thread state data structure.
847    In Python 3.6 and older, this function created the GIL if it didn't exist.
867    function can be called without holding the GIL, and therefore can be used to
871       The :term:`GIL` is now initialized by :c:func:`Py_Initialize()`.
934    When the function returns, the current thread will hold the GIL and be able
965    Return ``1`` if the current thread is holding the GIL and ``0`` otherwise.
968    holding the GIL will it return ``1``.
971    knowing that the GIL is locked can allow the caller to perform sensitive
1016    :c:func:`Py_Initialize()` now initializes the :term:`GIL`.
1114    The caller must hold the GIL.
1124    The caller must hold the GIL.
1181    must write your own C extension to call this.  Must be called with the GIL held.
1417    To call this function in a subinterpreter, the caller must hold the GIL.
1557    The caller must hold the :term:`GIL`.
1569    The caller must hold the :term:`GIL`.
1625 The GIL does *not* need to be held when calling these functions; they supply