Really? Is this the worse thing ever? How many of us building heavily threaded I/O bound applications are truly hampered by this? Yes; this sucks for CPU bound applications, that's been known since the earth cooled.
I, and many others, have been using threads in python w/o issue, now that multiprocessing is in core, when I do run into a limitation, I simply swap out the imports in many cases. On Fri, Jun 12, 2009 at 11:16 AM, Pete<[email protected]> wrote: > I didn't attend last night's UG, but I saw Dave give a version of this talk > about a month ago. I'll second Carl's opinion - this talk is of critical > importance to anyone using threads in Python. > > Begin forwarded message: > >> From: Carl Karsten <[email protected]> >> Date: June 12, 2009 10:51:33 AM EDT >> To: The Chicago Python Users Group <[email protected]> >> Subject: Re: [Chicago] Posted : Video >> >> * David Beazley: mind-blowing presentation about how the Python GIL >> actually works and why it's even worse than most people even imagine. >> http://blip.tv/file/2232410 http://www.dabeaz.com/python/GIL.pdf > > _______________________________________________ > concurrency-sig mailing list > [email protected] > http://mail.python.org/mailman/listinfo/concurrency-sig > _______________________________________________ concurrency-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/concurrency-sig
