Where do you see this happening? All I see are people and organizations deciding that they don't want to do the work of maintaining Python 2.
It's not a tragedy, backwards-compatibility is a burden, and I understand maintainers, especially volunteers not wanting to do it. But migration is a pain, I found the conversion was not too hard, but testing the migrated scripts for breakage was time consuming.
FYI, the cause of my latest migration was that the latest version for the mysql-connector for python no longer works with 2.7. See the changelog entry for v8.0.24 here: https://github.com/mysql/mysql-connector-python/blob/master/...
So something to consider if you want to stay on Python 2 forever.
Python 2.7 is not getting any security/crypto updates backported. Eventually PyPI's SSL configuration will change to a point where Python 2.7 won't handle it and then that's it. Game over, no more pip for you, even if you froze on < 21.0.
There are Linux distros out there in LTS until late into this decade that shipped with Python 2.7. Ubuntu 18 comes to mind, which EOLs in 2028. They've got a real hard problem to solve.
You can maintain Python 2 yourself just fine, though, if you like.
There are several projects out there that are supporting python 2.7 with security updates. Tauthon is probably the biggest one.
It appears to only take away from people the option to use the unmaintained Python 2.
Btw you can still return your copy of Python for a full refund.
Just because Python core can say that they support for five years and act like they're being generous when they do so does not make them less like asshats. Most software is not a living, breathing thing.
Is your budget going at all to maintaining Python 2 or the ancient Django you use? I'm gonna guess not.
We all know about how COBOL is alive and kicking but Python's core team decided that reality doesn't apply to them.
Maintaining Python 2 indefinitely is an option actively being taken away from people. More importantly, fuck anyone who wants to direct my budget! There's things written in Python 2 ages ago that don't justify additional developer time in my company. Except the community is making us do it.
If you think migrating some ancient Django app to modern Django is trivially easy, why don't you come do it for us?