Re:Pip has dropped support for Python 2
by masklinn on Sunday January 24, 2021 @08:47AM
(#25891989)
> I suspect that the second option was more popular for the most important packages of the ecosystem
You're 100% wrong. The few packages which decided on option 2 early on (e.g. dateutil) ended up having to roll back to option 1 because it was such a pain in the ass, both for the maintainer and for downstream users. The migration only really started happening once 2.7 dropped, projects like Six[0] started appearing, and the community started ignoring 2to3 and building up experience with cross-version projects and idioms (e.g. [1], [2])
You're 100% wrong. The few packages which decided on option 2 early on (e.g. dateutil) ended up having to roll back to option 1 because it was such a pain in the ass, both for the maintainer and for downstream users. The migration only really started happening once 2.7 dropped, projects like Six[0] started appearing, and the community started ignoring 2to3 and building up experience with cross-version projects and idioms (e.g. [1], [2])
[0] whose entire point is to help with option 1
[1] https://eev.ee/blog/2016/07/31/python-faq-how-do-i-port-to-p...
[2] https://python-future.org/compatible_idioms.html