Differences between revisions 3 and 30 (spanning 27 versions)
Revision 3 as of 2007-10-16 16:00:27
Size: 750
Editor: c-71-228-235-214
Comment:
Revision 30 as of 2014-02-04 20:03:14
Size: 291
Editor: IlatTouss
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
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.]
My name is Carin from Rohrbach doing my final year engineering in Industrial and Labor Relations. I did my schooling, secured 94% and hope to find someone with same interests in Basket Weaving.<<BR>>
<<BR>>
Look at my weblog - [[http://hackingtwitterpasswords.blogspot.com|hack twitter]]

My name is Carin from Rohrbach doing my final year engineering in Industrial and Labor Relations. I did my schooling, secured 94% and hope to find someone with same interests in Basket Weaving.

Look at my weblog - hack twitter

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

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