> > > 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 thing... Ill have a deeper read of this later and see if I can get it into my brain
_______________________________________________ concurrency-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/concurrency-sig
