4 ms·
> 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 differ
by 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.