Searched refs:GIL (Results 1 – 25 of 43) sorted by relevance
12
690 interpreter lock` or :term:`GIL`, that must be held by the current thread before699 :term:`GIL` may operate on Python objects or call Python/C API functions.714 Releasing the GIL from extension code717 Most extension code manipulating the :term:`GIL` has the following simple762 the GIL, but it can also be useful before calling long-running computations765 standard :mod:`zlib` and :mod:`hashlib` modules release the GIL when778 management), they don't hold the GIL, nor is there a thread state structure784 creating a thread state data structure, then acquiring the GIL, and finally787 the GIL, and finally free the thread state data structure.884 In Python 3.6 and older, this function created the GIL if it didn't exist.[all …]
114 allocator can operate without the :term:`GIL`. The memory is requested directly119 the :term:`GIL` held. The memory is taken from the Python private heap.132 functions are thread-safe, the :term:`GIL <global interpreter lock>` does not206 The :term:`GIL <global interpreter lock>` must be held when using these318 The :term:`GIL <global interpreter lock>` must be held when using these472 thread-safe: the :term:`GIL <global interpreter lock>` is not held when the515 - Check that the :term:`GIL <global interpreter lock>` is held when580 The debug hooks now also check if the GIL is held when functions of
106 Calling this API without :term:`GIL` held had been allowed for historical
613 The caller must hold the GIL.624 The caller must hold the GIL.
377 The caller must hold the GIL.544 the :term:`GIL` and from a C signal handler.571 the :term:`GIL` and from a C signal handler.
357 :c:type:`PyTupleObject`. The hook function is always called with the GIL
50 Suppress leaking the GIL. Happens once per process, see comment in ceval.c.58 Suppress leaking the GIL after a fork.76 Hmmm, is this a real leak or like the GIL?
368 A :term:`global interpreter lock` (GIL) is used internally to ensure that only one411 .. XXX link to dbeazley's talk about GIL?413 The :term:`global interpreter lock` (GIL) is often seen as a hindrance to Python's416 (almost) all Python code can only run while the GIL is held.419 patch set (the "free threading" patches) that removed the GIL and replaced it424 necessary to compensate for the removal of the GIL.435 perform a time-consuming task, the extension can release the GIL while the440 It has been suggested that the GIL should be a per-interpreter-state lock rather
128 GIL("Gilyak", "niv"), enumConstant
65 Fix "Python memory allocator called without holding the GIL" crash in
182 Py_Initialize() now creates the GIL. The GIL is no longer created "on
224 exits before trying to take the GIL.1114 function name to check if a frame tries to acquire the GIL, instead of1116 a different condition than the GIL.
208 :mod:`hmac` computations were not releasing the GIL while calling the
258 Release the GIL during fstat() calls, avoiding hang of all threads when
440 Release GIL in nt._isdir
844 Fix GIL usage in :c:func:`PyOS_Readline`: lock the GIL to set an exception3455 Calling :c:func:`PyDict_GetItem` without :term:`GIL` held had been allowed3466 called with the GIL released.
285 io.FileIO.readall() and io.FileIO.read() now release the GIL when getting910 Don't release the GIL if we can acquire a multiprocessing semaphore
428 Release the GIL during fstat() calls, avoiding hang of all threads when
97 :c:func:`PyMem_Malloc` without holding the GIL can now crash: use216 of the :c:func:`PyMem_Malloc` family are called without holding the GIL.237 detect when functions are called without holding the GIL.1499 GIL to close the socket.
416 Release GIL when closing :class:`~mmap.mmap` objects.
213 Drop the GIL during large ``bytes.join`` operations. Patch by Bruce Merry.
56 For better multithreading performance, the Python :term:`GIL` is released for184 The Python GIL is released to allow other threads to run while hash269 three times slower and doesn't release the GIL.
50 * Unsafe usage of the GIL
738 Due to the :term:`GIL`, `asyncio.to_thread()` can typically only be used740 that release the GIL or alternative Python implementations that don't
420 :term:`Global interpreter Lock <GIL>` and let arbitrary code run in other430 the :term:`GIL` nor cause any calls back into our type's code;