Python 3.2 Eases Concurrent Development

Re:Python 3.2 Eases Concurrent Development by StavrosK on Thursday December 09, 2010 @07:07AM (#1987095)

Unfortunately, I'm afraid the post might be excessively optimistic. PyPy doesn't have a GIL, does it? I really hope it becomes the standard Python at some point, especially with all the progress they've been making lately...

[ Parent | on HN ]

Re:Python 3.2 Eases Concurrent Development by thristian on Thursday December 09, 2010 @08:02AM (#1987225)

The PyPy FAQ[1] says: "Operating system-level threads basically work. If you enable the thread module then PyPy will get support for GIL based threading."

I had hoped that because PyPy uses a more sophisticated garbage-collector than CPython, it wouldn't need locking to update reference counts and hence wouldn't need a GIL (or wouldn't use it as much); I guess that's not the case (at least yet).

[1]: http://codespeak.net/pypy/dist/pypy/doc/faq.html#do-threads-...

[ Parent | on HN ]

Re:Python 3.2 Eases Concurrent Development by ominous_prime on Thursday December 09, 2010 @09:30AM (#1987521)

PyPy does have a GIL, but they are optimistic that their implementation will be easier to factor out in the future than CPython's.

[ Parent | on HN ]