Feb. 9, 2012
1:36 p.m.
On Fri, Feb 10, 2012 at 03:19:36AM +0800, Matt Joiner wrote:
The GIL annoys those who have learned to expect threading.Thread for CPU bound concurrency in advance -- which typically means prior experience with Java. Python threads are fine for their intended use -- e.g. I/O and background tasks in a GUI.
Even for that purpose they're too heavy. The GIL conflicts, and boilerplate overhead spawning threads is obscene for more than trivial cases.
The GIL is almost entirely a PR issue. In actual practice, it is so great (simple, straightforward, functional) I believe that it is a sign of Guido's time machine-enabled foresight. --titus -- C. Titus Brown, ctb@msu.edu