R. David Murray wrote:
> 
> R. David Murray <rdmurray@bitdance.com> added the comment:
> 
> Yes, it does:
> 
> rdmurray@maestro:~/python/py3k>ls -l ../ptest/p3/bin total 7328
> -rwxr-xr-x 1 rdmurray rdmurray     131 Dec 20 12:22 2to3
> -rwxr-xr-x 1 rdmurray rdmurray     119 Dec 20 12:22 idle3
> -rwxr-xr-x 1 rdmurray rdmurray     104 Dec 20 12:22 pydoc3
> -rwxr-xr-x 2 rdmurray rdmurray 3736249 Jan 13 12:43 python3
> lrwxrwxrwx 1 rdmurray rdmurray      16 Jan 13 12:44 python3-config -> python3.2-config
> -rwxr-xr-x 2 rdmurray rdmurray 3736249 Jan 13 12:43 python3.2
> -rwxr-xr-x 1 rdmurray rdmurray    1421 Jan 13 12:44 python3.2-config
> 
> That's a straight 'make install' from my svn checkout of the py3k trunk.

Sorry, forgot about that change. The name of the binaries is changed
during installation - after running 'make' you get a 'python' binary.

I wonder whether anyone has ever tried building Python on AIX.
Renaming binaries after linking is a bad idea on AIX, since the
linker then sometimes fails to resolve symbols.

I'm still -1 on the change.

People setting up PYTHONPATH will know what they are doing and also
know which Python version they are going to use with the customized
setting and after the transition from Python 2 to 3 we'd be stuck
with user environment setups using PYTHON3PATH instead of PYTHONPATH,
so removing PYTHON3PATH again won't be easily possible.

Besides, if you change PYTHONPATH, you'd also have to change
PYTHONHOME, PYTHONSTARTUP, and all the other flags to use
the 'PYTHON3' prefix.