[Python-Dev] 2to3 porting HOWTO: setup.py question (original) (raw)
Michael Foord fuzzyman at voidspace.org.uk
Tue Jul 24 12:07:42 CEST 2012
- Previous message: [Python-Dev] 2to3 porting HOWTO: setup.py question
- Next message: [Python-Dev] 2to3 porting HOWTO: setup.py question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 24 Jul 2012, at 10:30, Terry Reedy wrote:
On 7/24/2012 12:44 AM, anatoly techtonik wrote:
Python 3 check explicitly tells the reader that 2to3 should only be used in Python 3. Otherwise everybody need to guess when this *2to3 tools are triggered. As for me, I see no technical limitations why *2to3 can not be run by Python 2 (PyPy, RPython or whatever). Maybe I don't have Python3, but want to build my package for Python 3. In ideal world it is possible. This is not an ideal world and 2to3 is not good enough to convert files without further intervention and testing.
It is if you design your code to be converted by 2to3 and do regular testing of the result.
Michael
-- Terry Jan Reedy
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
-- http://www.voidspace.org.uk/
May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html
- Previous message: [Python-Dev] 2to3 porting HOWTO: setup.py question
- Next message: [Python-Dev] 2to3 porting HOWTO: setup.py question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]