On Sat, Apr 18, 2009 at 10:04 PM, 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
Thanks for the clear explanation. The fact that "python" still appears
with "fullinstall" covers my concern.
> With that setup, I'm sure we're going to get people complaining that
> 'altinstall' of 3.2 broke their python3 symlink from 3.1. If there are
> going to be 3 levels of executable naming (python3.x, python3, python),
> there needs to be 3 levels of installation rather than the traditional 2.
>
> For example, add a new target "py3install" and make that the default for
> 3.1:
>
> 3.x altinstall:
> - installs python3.x executable
>
> 3.x py3install (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
Yep, I agree this is what needs done to sensibly support a "python3".
Steve
--
I'm not *in*-sane. Indeed, I am so far *out* of sane that you appear a
tiny blip on the distant coast of sanity.
--- Bucky Katt, Get Fuzzy
_______________________________________________
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
