News for hackers. Stuff that matters.
Re:The first stable release of PyPy3 by derengel on Friday June 20, 2014 @06:06PM (#7923165)
I don't know or use Python but why an implementation that is trying to be "superior" still has the GIL?
Re:The first stable release of PyPy3 by huxley on Friday June 20, 2014 @06:15PM (#7923201)
This donation page has some background on how PyPy is proposing to replace the GIL with software transactional memory:

http://pypy.org/tmdonate2.html#introduction

Re:The first stable release of PyPy3 by pekk on Friday June 20, 2014 @07:09PM (#7923406)
What DO you know or use? Did you think that the GIL was an obvious and stupid oversight made by stupid people for no good reason?
Re:The first stable release of PyPy3 by glibgil on Friday June 20, 2014 @09:10PM (#7923750)
Obviously the GIL was shortsighted, yes. Leave the people out of it. The idea was stupid. There was a reason, but it wasn't a good reason.
Re:The first stable release of PyPy3 by rguillebert on Friday June 20, 2014 @09:56PM (#7923856)
What would you replace it with ?
Re:The first stable release of PyPy3 by glibgil on Saturday June 21, 2014 @12:56AM (#7924241)
No GIL.
Re:The first stable release of PyPy3 by rspeer on Saturday June 21, 2014 @03:28AM (#7924428)
Your username is apt, but novelty accounts aren't a thing here. What exactly are you hoping to communicate?
Re:The first stable release of PyPy3 by glibgil on Saturday June 21, 2014 @04:35PM (#7925996)
My name is Gil. Look at my comment history and apologize.
Re:The first stable release of PyPy3 by rguillebert on Saturday June 21, 2014 @08:47AM (#7924830)
you need something to allow concurrent access to internal interpreter data structures...
Re:The first stable release of PyPy3 by glibgil on Saturday June 21, 2014 @04:35PM (#7925999)
STM or MVar
Re:The first stable release of PyPy3 by meowface on Friday June 20, 2014 @06:58PM (#7923378)
Because it's very tricky to remove.

Ruby also has a GIL.

Re:The first stable release of PyPy3 by dragonwriter on Friday June 20, 2014 @07:21PM (#7923449)
> Ruby also has a GIL.

MRI has a GIL; major alternative implementations (JRuby, Rubinius) do not.

OTOH, addressing the downsides of a GIL are not the only reasonable motivations for an alternative implementation, so there's no reason that a better-than-stock Python (or Ruby) fundamentally must remove the GIL (the current "MRI" used to be an alternative, YARV, to the old MRI, and both had GILs.)

Re:The first stable release of PyPy3 by meowface on Friday June 20, 2014 @09:06PM (#7923741)
True. Jython and IronPython also do not have a GIL.