Differences between revisions 2 and 3
Revision 2 as of 2007-03-09 16:56:56
Size: 322
Editor: CameronLaird
Comment:
Revision 3 as of 2007-10-16 16:00:27
Size: 750
Editor: c-71-228-235-214
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
"[http://docs.python.org/api/threads.html Global interpreter lock]" [explain] In CPython, the '''global interpreter lock''', or '''GIL''', is a mutex that prevents multiple native threads from running Python code at once. This lock is necessary mainly because CPython's memory management is not thread-safe. (However, since the GIL exists, other features have grown to depend on the guarantees that it enforces.)

CPython extensions must be GIL-aware in order to avoid defeating threads. For an explanation, see [http://docs.python.org/api/threads.html Global interpreter lock].

In CPython, the global interpreter lock, or GIL, is a mutex that prevents multiple native threads from running Python code at once. This lock is necessary mainly because CPython's memory management is not thread-safe. (However, since the GIL exists, other features have grown to depend on the guarantees that it enforces.)

CPython extensions must be GIL-aware in order to avoid defeating threads. For an explanation, see [http://docs.python.org/api/threads.html Global interpreter lock].

... [much to say]

One of IronPython's delights is that it works around the GIL; IronPython-based applications can be fully-threaded in the sense that they properly exploit multi-core CPUs.

[Mention place of GIL in StacklessPython.]

GlobalInterpreterLock (last edited 2020-12-22 21:57:53 by eriky)

Unable to edit the page? See the FrontPage for instructions.