> Maintaining Python 2 indefinitely is an option actively being taken away from people
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.
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.
There are several projects out there that are supporting python 2.7 with security updates. Tauthon is probably the biggest one.
You can maintain Python 2 yourself just fine, though, if you like.
It appears to only take away from people the option to use the unmaintained Python 2.