3 ms·
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
by zabbadabba 11y ago
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.
- pekk 11y agoPython 3 wasn't really starting anew, they were also balancing the ongoing screaming about every difference from Python 2.
- zabbadabba 11y agoIt 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.
- ericsnow 11y agoyou forgot your <hand-wavy gross exaggeration> tags