In article <49eab0c2.8040...@gmail.com>, Nick Coghlan <ncogh...@gmail.com> wrote: > Steven Bethard wrote: > > On Sat, Apr 18, 2009 at 9:37 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > >> Note that such an approach would then require an altaltinstall command > >> in order to be able to install a specific version of python 3.x without > >> changing the python3 alias (e.g. installing 3.2 without overriding 3.1). > > > > I wasn't suggesting that there shouldn't be a "python3.1", > > "python3.2", etc. I'm more concerned about "fullinstall" creating > > "python3" instead of regular "python". > > If I understand Tony's summary correctly, the situation after Benjamin's > latest checkin is as follows: > > 2.x altinstall: > - installs python2.x executable > > 2.x fullinstall (default for "make install"): > - installs python2.x executable > - adjusts (or creates) python symlink to new executable > > 3.x altinstall (default for "make install"): > - installs python3.x executable > - adjusts (or creates) python3 symlink to new executable > > 3.x fullinstall: > - installs python3.x executable > - adjusts (or creates) python3 symlink to new executable > - adjusts (or creates) python symlink to new executable
Note that versioning is also an unresolved issue for the scripts installed by setup.py; pydoc, idle, 2to3, and smtpd.py. See: http://bugs.python.org/issue5756 Whatever is implemented for python itself should likely apply to them as well. -- Ned Deily, n...@acm.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
