4 ms·
worth noting that in the python 2 to 3 story, a migration path was mostly provided along with tools that tried to automatically refactor your code, the latest 2
by znpy 6y ago
worth noting that in the python 2 to 3 story, a migration path was mostly provided along with tools that tried to automatically refactor your code, the latest 2.x release was supported for nearly a decade, and there have been directions on how to temporarily write code to work on both python2 and python3.
- sergeykish 6y agoPython 3 is only unusual in its failure. Perl6 Apocalypses [1] is wonderful. Python 3000 is pointless [2]. I've been Python developer at that time, the writing was on the wall. They have not provided migration path. PEP 414 "Complaint: This PEP may harm adoption of Python 3.2" [3], this is insane. Community voted with feet — they've stayed with Python 2 until clean migration path arrived. I've switched to Ruby and been happy since. Ruby 1.8.7 was supported for five years. You had to write Python 2 code and run 2to3, you had to live in the past or abandon it. [1] https://raku.org/archive/doc/apocalypse.html https://raku.org/archive/doc/apocalypse.html [2] https://en.wikipedia.org/wiki/History_of_Python#Features https://en.wikipedia.org/wiki/History_of_Python#Features [3] https://www.python.org/dev/peps/pep-0414/ https://www.python.org/dev/peps/pep-0414/