[Python-Dev] #!/usr/bin/env python --> python3 where applicable (original) (raw)
Ned Deily nad at acm.org
Sun Apr 19 09:26:13 CEST 2009
- Previous message: [Python-Dev] #!/usr/bin/env python --> python3 where applicable
- Next message: [Python-Dev] #!/usr/bin/env python --> python3 where applicable
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <49EAB0C2.8040506 at gmail.com>, Nick Coghlan <ncoghlan at gmail.com> wrote:
Steven Bethard wrote: > On Sat, Apr 18, 2009 at 9:37 PM, Nick Coghlan <ncoghlan at 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, nad at acm.org
- Previous message: [Python-Dev] #!/usr/bin/env python --> python3 where applicable
- Next message: [Python-Dev] #!/usr/bin/env python --> python3 where applicable
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]