I will cede that there are non-hostile areas where Python 2 could run forever. The same sort of environments where FORTRAN have rumbled on forever. And I agree

I will cede that there are non-hostile areas where Python 2 could run forever. The same sort of environments where FORTRAN have rumbled on forever. And I agree that there are other hostile environments where some organisations have completely the wrong priorities. Desktops and networks and traffic management rarely seem to be perfect. But on Python, I think many people underappreciate the attack surface. Just because it's not a server doesn't mean you can't feed it a malformed JPEG, or funky bytestring that causes it to blow up and spawn shells. It's a similar problem to PHP in that python includes so many batteries, it's trivial for attackers to branch out. And much of this frustration —which leads to the strength of language— is that we bump into clients and clients' developers who proudly announce they're running a stack 4 years out of date. It's stupid the number of times I've had to explain why this is a bad idea. I've even had to demonstrate deep hacks (with permission, and remuneration) to clients who think they're immune "because Linux" or whatever. Basically they didn't want to pay their technical debt until they can see a 12yo Ukrainian (not important) kid could destroy their whole company.