5 ms·

Lots of things didn't upgrade because their dependencies didn't. And the dependencies had no reason to, because 3.0 didn't offer anything they didn't have befor

• BeetleB 5y ago
  Quite a bit before the deadline, pretty much all dependencies had upgraded. Those that hadn't were more or less abandoned projects. Sure, you could hunt and find some that were still maintained/developed with Python 2 in, say, 2019. But these again will be the tiny minority. I still stand by my 1% claim. The problems with upgrading have been vastly exaggerated.
  • JanisL 5y ago
    The pain in the Python 2->3 conversion I found came more from in house packages being written in Python 2 rather than public packages.