Re:A viable solution for Python concurrency
by snovv_crash on Saturday October 16, 2021 @04:14AM
(#28886333)
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 before.
Re:A viable solution for Python concurrency
by BeetleB on Saturday October 16, 2021 @01:07PM
(#28889338)
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.
Sorry, but that's fiction. Yes, lots of projects (still the minority) simply didn't upgrade, but it's not because they tried and failed. It's because they never prioritized it.
> Here's a pain story about a 2 to 3 migration though:
Consistent with my claim:
> Probably less than 1% of projects had serious issues with the migration. We just hear of a few popular ones that had some pain and assume that was representative.