4 ms·
My main concern that's stopping me from using Python 3 for all new projects is the risk of being in the middle of the project, and finding yourself needing a li
by john2x 11y ago
My main concern that's stopping me from using Python 3 for all new projects is the risk of being in the middle of the project, and finding yourself needing a library only to find out that it only works on Python 2.
Couple that with 2.7 being good enough just makes the situation "worse" for 3.
- netheril96 11y agoI was a staunch Python 3 supporter until I encountered such a thing. I avoid Python 3 now because I don't want to be forced to make a decision between writing the requisite library myself (a huge undertaking), abandoning the project entirely, or rewriting everything into Python 2 again. Better to just start with Python 2 in the first place.
- collinmanderson 11y agoI'm curious: what libraries still need porting? I feel like at this point most major libraries are either ported or have an easy fork/alternative.
- lmm 11y agoIf you're using any language other than C you'll always occasionally find yourself in the situation of "there's this useful library that only exists in C". But for many languages the library ecosystem is large enough, and the language better by C than enough, for the tradeoff to be worth it. Also that's kind of what this post is about. Pretty soon there'll be a bigger risk of finding that some library you want is Python3-only than finding that some library you want is Python2-only.
- plorkyeran 11y agoEven when writing C you still occasionally find yourself in the situation of "there's this useful library that only exists in Java". There's no language that can directly use every single specialized niche library written by a domain expert.