News for hackers. Stuff that matters.
Re:Solving multi-core Python by zabbadabba on Thursday July 09, 2015 @11:14PM (#9862106)
Avoiding fixing the C API for the sake of backwards compatibility is the reason for the GIL mess. Python 3 had a chance to correct the API situation since they were starting anew, but it didn't happen. All these API half measures are just dancing around the real problem of not having truly independent interpreter instances.
Re:Solving multi-core Python by pekk on Friday July 10, 2015 @12:44AM (#9862338)
Python 3 wasn't really starting anew, they were also balancing the ongoing screaming about every difference from Python 2.
Re:Solving multi-core Python by zabbadabba on Friday July 10, 2015 @10:14AM (#9864043)
It is curious how they completely revamped Python making most Python3 code incompatible with Python2 and yet they wanted to preserve C API "compatibility". Compatibility with what? Most Python3 modules had to be rewritten anyway - it was the perfect opportunity to fix the C API and get rid of the GIL once and for all.
Re:Solving multi-core Python by ericsnow on Friday July 10, 2015 @12:21PM (#9864869)
you forgot your <hand-wavy gross exaggeration> tags