I've been listening to this nonsense for at least the last three years since I have a few clients heavily vested in Python.
Two comments in Drew Crawford's article say it all AFAIC.
Articles like Alex’s suggest the solution is to fork:
One solution is to fork Python 2.7, and continue developing the language, adding features in a backwards compatible way so large, unportable (due to financial constraints) Python 2 applications can continue to evolve and improve and bring value to the people and companies that invested so much time developing them. This is the correct thing to do (actually, it would be best if Guido and other leaders in the Python community did this officially instead of forcing a fork).
Maybe Alex missed it, but here’s the button:
A python fork
You don’t need permission. You don’t need to argue with anybody. Just do it! It’s not that hard.
Bingo! SO...you've spent a whole lot of effort not
keeping up with the state of the language and now have a bunch of projects you
are making good money off of using the old version? And it is your god-given right, to say nothing of your moral privilege, to demand
that somebody who is doing this all for free
priorities and goals so you
can continue to do so? Puh-leez!
Blog posts aren’t demand. Demand is people willing to develop. Demand is people willing to fund development. I’d even settle for a $15 themeforest splash page that lists one corporate sponsor and one developer’s bio. How is it that Python is somehow in grave danger of forking and nobody will even buy a domain name for the fork? People literally do that for a weekend hack project. This is a tempest in a teacup if I’ve ever seen one.
Yup. Far too many tech bloggers go on a rant and somehow start to believe they're "speaking for The People" or "The Working Man."
Apparently the project developers they're targeting don't fall under that mantle of righteousness because they just do the actual work
rather than hold "informed" opinions about it.
Tempest in a teacup it is. And one that's all too common in the FOSS world where this rampant sense of entitlement
is the unfortunate norm.
(Note: I've coded Python in both v2 and v3 - and I really can't see where v2 is provably better. But I'm not a real programmer so that might be attributable to ignorance on my part. My clients, however, are very
qualified programming professionals. And both started migrating their codebases over to using Python-3 as soon as it was deemed stable enough to do so. So make of that
what you will.