5 ms·
I don't know or use Python but why an implementation that is trying to be "superior" still has the GIL?
by derengel 12y ago
I don't know or use Python but why an implementation that is trying to be "superior" still has the GIL?
- huxley 12y agoThis donation page has some background on how PyPy is proposing to replace the GIL with software transactional memory: http://pypy.org/tmdonate2.html#introduction http://pypy.org/tmdonate2.html#introduction
- meowface 12y agoBecause it's very tricky to remove. Ruby also has a GIL.
- dragonwriter 12y ago> 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.)
- pekk 12y agoWhat 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?
- glibgil 12y agoObviously 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.
- rguillebert 12y agoWhat would you replace it with ?
- glibgil 12y agoNo GIL.
- rspeer 12y agoYour username is apt, but novelty accounts aren't a thing here. What exactly are you hoping to communicate?
- glibgil 12y agoMy name is Gil. Look at my comment history and apologize.
- rguillebert 12y agoyou need something to allow concurrent access to internal interpreter data structures...
- glibgil 12y agoSTM or MVar