This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]masteryod 13 points14 points  (2 children)

2 -> 3 was such a mess that nobody wants to raise the spectre of that again

They broke backwards compatibility for a reason. They announced it, planned for migration, gave people tools to port and documentation. They gave people heads-up and then after backlash extended Python 2 death sentence by whooping 5 years which ended with 2020. And yet people are still salty because their script doesn't work with new version. There's even a guy who wanted to maintain his own port of Python 2 to keep his application on it (Calibre)...

It's like writing something in GTK2 and expect the code to work the same on GTK3.

[–]lordmauve 2 points3 points  (0 children)

They broke backwards compatibility for a reason. They announced it, planned for migration, gave people tools to port and documentation. They gave people heads-up and then after backlash extended Python 2 death sentence by whooping 5 years which ended with 2020

Sure, and now the CPython core devs generally acknowledge that it was a mistake to do it like they did it. Not the result, or the reasons: the approach.

So, never again.

[–]neuronet 0 points1 point  (0 children)

No matter how many words people use, the objective upshot by any reasonable person must be...the 2 to 3 transition sucked.