At 08:27 AM 4/22/2009 +0200, Lennart Regebro wrote:
On Tue, Apr 21, 2009 at 19:57, P.J. Eby <p...@telecommunity.com> wrote:
> At 04:06 PM 4/21/2009 +0200, Lennart Regebro wrote:
>>
>> On Tue, Apr 21, 2009 at 15:03, P.J. Eby <p...@telecommunity.com> wrote:
>> > python2 setup.py 2to3 test
>>
>> Well, yes, but it should be
>>
>> python 3 setup.py 2to3 test
>>
>> Otherwise it can't reasonably have any idea of which python to use.
>
> Why not? The 2to3 command could simply take an option for the python3
> executable, and be set from the standard config files (e.g. setup.cfg).
Because that would mean that Python 2 needs to be installed to use
Python 3. It also means all programs that do any sort of installing
need to either know the position of the python 3 executable to use
when installing, and be run with Python 2, or they need to be run with
Python 3 and know the position of a Python 2 interpreter to run
setup.py with.
Er, no. It only means that you need Python 2 to be installed *while
porting a package* to Python 3.
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
