3 ms·
Alternative view titles: Zero - The Number of Applications that Can only be Developed in Python 3 or 7456324 - The number of companies that only use Python 2
by SeanDav 9y ago
Alternative view titles:
Zero - The Number of Applications that Can only be Developed in Python 3
or
7456324 - The number of companies that only use Python 2.x
Although these made up titles are slightly tongue-in-cheek, they do server to illustrate that for me at least, I do not have a compelling reason to switch to Python 3.
- teilo 9y agoThat's also a meaningless argument. It's true of any turing-complete language.
- SeanDav 9y ago> "That's also a meaningless argument. It's true of any turing-complete language." Title 1 of course. Title 2 is a far more compelling reason to stay with Python 2.x. If I program for fun, then Python 3 is definitely worth playing around in, but for professional development, everything I do in Python is done in Python 2.x. That is not a theoretical argument, that is fact.
- minitech 9y ago> for professional development, everything I do in Python is done in Python 2.x. That is not a theoretical argument, that is fact. And everything I do professionally in Python is done in 3.x as of this January. Also fact! Industry standards sometimes move slowly, but they are moving.
- teilo 9y agoThat is only relevant if there is no significant professional Python 3.x development taking place. There is, in fact, significant 3.x development taking place, and that number is growing - exactly as one would expect. And by significant, I mean upwards of 40%. So, except for corporate inertia, or the rare can't-live-without libraries that have yet to be ported to 3.x (see: http://py3readiness.org http://py3readiness.org), there are no compelling reasons to stick with Python 2.x for new projects.