Feb. 9, 2012
3:05 p.m.
On Fri, Feb 10, 2012 at 5:19 AM, Matt Joiner <anacrolix@gmail.com> 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.
Have you even *tried* concurrent.futures (http://docs.python.org/py3k/library/concurrent.futures)? Or the 2.x backport on PyPI (http://pypi.python.org/pypi/futures)? Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia