3 ms·
The Python 2 to 3 transition took a while, but I'd say it was successful in the end, wasn't it?
by eru 4y ago
The Python 2 to 3 transition took a while, but I'd say it was successful in the end, wasn't it?
- oblio 4y agoThere are some arguments to be made they didn't break enough. For example: - I think they bungled the Unicode transition by being too dogmatic and it took them a few point releases to include some quality of life improvements for migration that really allowed legacy libraries to transition - the GIL dependency didn't go away - typing was added later Python 3 would have been a huge jump with those changes. Instead, Python 3.0 was very interesting but a major annoyance for limited benefits to 99% of Python app devs.
- eru 4y agoI agree with your points. There's some serious work going on with the GIL these days. And also about immutability and reducing reference counting. > [...] it took them a few point releases to include some quality of life improvements for migration that really allowed legacy libraries to transition I wouldn't hold that against the transition too much. No one gets everything right from the start. About typing: owing to Python's culture, I don't think mainstream Python will be statically typed by default (or even obligatorily) anytime soon.
- deadbeeves 4y agoThat would imply that it actually finished, which is not obvious to me. The last time I found Python 2 code must have been a few months ago, and I'm not a regular Python user. And that's kind of the problem: old code never just goes away. It lingers until you try to compile it and it fails.
- eru 4y agoIsn't that the same with old versions of eg C++?
- JohnFen 4y agoIt successfully messed up a bunch of stuff on my machines, and successfully got me to stop using Python entirely.