2to3?
2to3?
Posted May 22, 2025 17:15 UTC (Thu) by mb (subscriber, #50428)In reply to: 2to3? by zahlman
Parent article: Recent disruptive changes from Setuptools
>And I still don't.
Big break-the-world changes are bad, because they cost a lot of time at once to fix and a lot of money at once to fix.
For me it is easy to make small deprecation removal changes together with the required feature development. I don't have to ask for additional time or money. It can be done during the normal development process and nobody complains.
But it is *much* harder to get time and money for doing the one big major-version-bump transition that broke the world.
For lots of projects that's basically impossible to do.
I still maintain Python 2 scripts and they will never be replaced with Python 3. Ever.
Python 2 code is even still being actively developed, because the whole ecosystem of the project is stuck at a Python 2 interpreter. And that also will not change for these projects. Ever.
Python 2 will have to die no earlier than the projects that still use it.
Please don't do this mistake with anything ever again.