3 ms·

Everyone has different needs. For your needs (for most people's needs), Py3 is better. For his needs, Py2.7 is better. It's not hard to understand. If everythi

Everyone has different needs. For your needs (for most people's needs), Py3 is better. For his needs, Py2.7 is better. It's not hard to understand. If everything he encounters, for example, is in 2.7, then that's probably the best tool for the job. If I'm commuting to work in the morning, I want a nice sedan with an automatic transmission and fuel injection because it's nice and modern and easy to use. If I'm in rural Africa though, I probably want a truck with a manual transmission and a carburetor. Sure it's outdated, but if I need a mechanic to work on it or parts that will fit it, every other car on the road there is just as outdated as mine.

BerislavLopac 10y ago
> If everything he encounters, for example, is in 2.7, then that's probably the best tool for the job. I disagree. Your example describes two completely different solutions to different scenarios; but Python 3 is not a different solution, it's a subset. It has everything that 2.7 has, only improved -- which means that for each case that Py 2.7 can handle, Py 3 can handle it just as easily, or better. My comment was simply about the phrase "the best tool for the job" -- Python 2.7 is in many cases good enough, and there is no point in switching an existing codebase if it means much more work than it brings benefits. However, when starting something new, with the goal of using "the best tool for the job", Python 3 is -- in my experience at least -- the clear winner.