Python 2 was originally going to be EOL'd in 2015, the announcement for which was in 2008. Only later was the EOL pushed back to 2020. So while it's only been o

Python 2 was originally going to be EOL'd in 2015, the announcement for which was in 2008. Only later was the EOL pushed back to 2020. So while it's only been officially "dead" for two years now, the writing had been on the wall for 12 years before that. At this point it is stubbornness - I know software doesn't magically get ported and updated as time goes on, but I also acknowledge that if no one cares to update the software (or provide a replacement) in a 14-year window then that is on that package's community rather than everyone else. The baseline should not be dragged down to accommodate legacy software. MacOS removing Python 2 support in a minor OS version bump was the wrong way of handling things, but in general you should not expect it to be available on modern platforms or be surprised at its removal (outside of pledged long-term support e.g. CentOS). And you can still use a VM or something, same as you would use DosBox to run old 16-bit software.