[Python-Dev] 2to3 porting HOWTO: setup.py question
Michael Foord
fuzzyman at voidspace.org.uk
Tue Jul 24 13:09:24 CEST 2012
More information about the Python-Dev mailing list
Tue Jul 24 13:09:24 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 11:52, Devin Jeanpierre wrote: > On Tue, Jul 24, 2012 at 6:07 AM, Michael Foord > <fuzzyman at voidspace.org.uk> wrote: >>> 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. > > That's hardly without testing! > Well, *no* code can safely be created without testing. The OP did say intervention *and* testing... Michael > -- Devin > -- 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 ]
More information about the Python-Dev mailing list