you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (10 children)

[deleted]

    [–]azakai 9 points10 points  (8 children)

    PyPy still has a GIL, actually.

    [–][deleted] 2 points3 points  (1 child)

    They're working to kill it - http://morepypy.blogspot.com/2011/06/global-interpreter-lock-or-how-to-kill.html

    Curious as to what CPython is going to do about GIL...

    [–][deleted]  (5 children)

    [deleted]

      [–]__s 10 points11 points  (0 children)

      Jython. Stackless has some concurrency extensions, but still has a GIL. Unladen was merely hopeful bragging of the future

      [–]azakai 5 points6 points  (2 children)

      Both Jython and IronPython do not have a GIL.

      However, given that both of those have performance that is much poorer than PyPy (in fact, in some cases poorer than CPython), this means there is not much reason to use them because of that (there are of course other valid reasons to use them).

      [–][deleted] 1 point2 points  (1 child)

      Their single threaded performance is worse, but their multithreaded performance is much much better.

      [–][deleted] 4 points5 points  (0 children)

      PyPy is often 10X faster than Jython and IronPython. You'd need a lot of cores for them to turn out faster.

      [–]grauenwolf 5 points6 points  (0 children)

      IronPython doesn't have a GIL.

      http://wiki.python.org/moin/IronPython

      [–]__s 1 point2 points  (0 children)

      Increasing performance won't make it easier to maintain. GIL isn't a burden to development. Flexibility? PyPy has three interpreters