5 ms·
Well, because you're developing against an unsupported runtime. No bug or security updates. If that's fine for you, feel free, otherwise get with the (supported
by newaccoutnas 7y ago
Well, because you're developing against an unsupported runtime. No bug or security updates. If that's fine for you, feel free, otherwise get with the (supported) program.
If it's a new project, there are no excuses imho
- newaccoutnas 7y agoIn addition I don't think you'd have to interrogate every line, depending on your codebase and upstream module support for Python 3. There are tools like: http://python-future.org/automatic_conversion.html http://python-future.org/automatic_conversion.html and https://python-modernize.readthedocs.io/en/latest/ https://python-modernize.readthedocs.io/en/latest/ Which should get you most of the way there. Look at https://docs.python.org/3/howto/pyporting.html https://docs.python.org/3/howto/pyporting.html for more info
- newen 7y agoI would argue I am coding against a stable runtime. No unexpected bugs due to upgrading. No need to worry about upgrading. For many applications, I don't have to worry about security updates. I think for many cases like closed systems that plan to run for years to decades, python 2 is attractive to even new projects.