On 15/07/2014 15:31, Chris Angelico wrote:
On Tue, Jul 15, 2014 at 11:57 PM, Kevin Walzer <k...@codebykevin.com> wrote:
I've stayed with Python 2.7 because I've seen no benefit in 3.x that
outweighs the hassle of going through my code line by line to make it
compatible.
And that's fine! The python-dev team has promised that 2.7 will
continue to be supported; that means some headaches, especially on
Windows (the Python 2.7 support will long outlast upstream Microsoft
support for the compiler it's built on), but it's a promise that you
can continue to run your 2.7 code.
That said, though, I would advise you to give 2to3 a shot. You never
know, it might do exactly what you need right out-of-the-box and give
you a 3.x-compatible codebase in one hit.
Or any one of
https://pypi.python.org/pypi/six/1.7.3
https://github.com/mitsuhiko/python-modernize
http://python-future.org/
https://github.com/nandoflorestan/nine
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
---
This email is free from viruses and malware because avast! Antivirus protection
is active.
http://www.avast.com
--
https://mail.python.org/mailman/listinfo/python-list
