[concurrency] Issues with the current concurrency mechanisms in Python

Christopher Reay christopherreay at gmail.com
Wed Feb 15 13:19:48 CET 2012

> > The issues here are that threading (certainly for Python) is
> > fundamentally limited to running on a single core, and can require
> > dancing around the GIL if multiple processes are accessing our
> > python state concurrently.
> This I either don't parse, or don't agree with. Python code can't run
> concurrently with other Python code - the GIL prevents it. PyPy with
> STM or Jython (which uses fine-grained locks) and C extensions in
> cPython that release the GIL can run concurrently, potentially on
> multiple cores.

I dont think I parse what you said either. Perhaps we are saying the same

Ill have a deeper read of this later and see if I can get it into my brain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/concurrency-sig/attachments/20120215/0693b95b/attachment.html>

More information about the concurrency-sig mailing list