Lesson for future: schedule incompatible changes for a reasonable schedule, and just move on. If Python2 was scheduled in 2007 to go EOL in 2009, not only Python dev team would have twice the resources but every single distro that maintained parallel 2/3 packages for 13 years.

I don't remember when I rewrote all my project to Python 3 - perhaps a decade ago.

If you think you can run an application with no maintenance for decades... well, good luck.

https://thenewstack.io/frustration-mounts-over-python-3-migrations/