3 ms·

I agree with what you say, but: > The maintainers would probably do some things different with the 2to3 conversion if they had to do it over again. Saying tha

I agree with what you say, but: > The maintainers would probably do some things different with the 2to3 conversion if they had to do it over again. Saying that "probably do some things different" is quite an understatement. Python 2 to 3 was an articulated train collision in slow motion that spans a decade. I'm sorry to say that, but it was monumentally awful. I really, really wish that it didn't happen because I think it kept Python back at least 5 years. People got really burnt by this upgrade process, and the answer was "we said we'd do backwards incompatible changes". "And what, are we going to have this every few years?" one might have though. So, it isn't enough to tell people to "stop complaining about Python 2to3" and things might be done differently in the future or past.

nindalf 5y ago
> it kept Python back at least 5 years. Yeah, it's done alright for itself hasn't it? Look at the stats, it's a top #2 language on Github, StackOverflow questions, Developer surveys or any other measure. Complaining that it could have achieved this 5 years earlier, I don't see the point. We can just appreciate where it's at now, and the people who were instrumental in getting us here.
Zababa 5y ago
> "And what, are we going to have this every few years?" Isn't this the current situation now? Granted, not as big as Python 2 to 3, but there are backwards incompatible changes often.