[Python-Dev] 2to3 porting HOWTO: setup.py question (original) (raw)
Éric Araujo merwok at netwok.org
Tue Jul 24 00:27:54 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 22/07/2012 15:57, R. David Murray wrote:
I'm not familiar with distutils, really, so you could be right about what it is important to test. I was commenting based on the code snippet presented, which just deciding which "build" object to use. If buildpy2to3 can be imported by python2 and subsequently screws up the build, then yes the logic is incorrect.
That can’t happen. The *_2to3 classes (don’t forget build_scripts_2to3) only exist in 3.x and work with a version check or an import with fallback. There is no cross-version-build at all in distutils.
Regards
- 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 ]