4 ms·
Removing the GIL is a difficult problem: http://python-notes.curiousefficiency.org/en/latest/python3/multicore_python.html http://python-notes.curiousefficiency
by svisser 11y ago
Removing the GIL is a difficult problem: http://python-notes.curiousefficiency.org/en/latest/python3/multicore_python.html http://python-notes.curiousefficiency.org/en/latest/python3/...
- criddell 11y agoI think the question was if you aren't going to be backwards compatible, why not unshackle yourself completely and design a new language without the GIL and make it as pythonic as possible? A scripting language that support multi-threading is possible, right? I think TCL does it.
- chrisseaton 11y agoI guess they were happy with breaking backwards compatibility a little bit, not not as much as simply removing the GIL and not adding back any implicit synchronisation at all.
- mkesper 11y agoI think this question can only be raised in hindsight. I think nobody suspected the unicode transition to be so slow and painful. As there probably won't be such a big transition evermore, I wouldn't hold my breath for it happening.