27 ms·
Getting rid of the GIL would warrant the release of Python 4.0 for me, except the Python project shouldn't be supporting two different branches for as long as t
by jeroenhd 3y ago
Getting rid of the GIL would warrant the release of Python 4.0 for me, except the Python project shouldn't be supporting two different branches for as long as they supported 2.7.
I imagine there would need to be some kind of annotation to enable the GIL for a method and all of the code it calls, including libraries, so performant Python can take advantage of the lack of a GIL but old code doesn't break. Then all you need to do to maintain compatibility is to annotate your main() and your code should remain compatible for a while.
After all, the referenced PEP explicitly calls for making the GIL optional, not for removing it completely.
- Valodim 3y ago"python 4", such a simple phrase yet sure to strike terror in the heart of many
- brianwawok 3y agoAs a Python dev who dealt with 2->3 not really.
- kelipso 3y agoEvery community has their masochists.
- imtringued 3y ago>Python project shouldn't be supporting two different branches for as long as they supported 2.7. That wasn't the problem. The problem was not giving people the ability to make their code python 3 compatible while they were still stuck with python 2. The python 3 interpreter should have had a python 2 mode that gives you warnings.
- jeroenhd 3y agoPython 2 and Python 3 were inherently incompatible for various reasons (good and bad ones). There were compatibility wrappers for porting Python 2 code to Python 3 but in some instances that was just never going to happen.