[Python-Dev] #!/usr/bin/env python -- python3 where applicable
Jared Grubb wrote: Ok, so if I understand, the situation is: * python points to 2.x version * python3 points to 3.x version * need to be able to run certain 3k scripts from cmdline (since we're talking about shebangs) using Python3k even though python points to 2.x So, if I got the situation right, then do these same scripts understand that PYTHONPATH and PYTHONHOME and all the others are also probably pointing to 2.x code? Would it make sense to introduce PYTHON2PATH and PYTHON3PATH (or even PYTHON27PATH and PYTHON 32PATH) et al? Or is this an area where we just figure that whoever moved the file locations around for distribution can hardcode things properly? -jJ ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Greg Ewing wrote: Steven Bethard wrote: That's an unfortunate decision. When the 2.X line stops being maintained (after 2.7 maybe?) we're going to be stuck with the 3 suffix forever for the real Python. I don't see why we have to be stuck with it forever. When 2.x has faded into the sunset, we can start aliasing 'python' to 'python3' if we want, can't we? You could, but it's not my favorite idea. Gets people used to the idea of python == python2 and python3 == python3 as something they can count on. Then says, Oops, that was just an implementation detail, we're changing that now. Much better to either make a clean break and call the new language dialect python3 from now and forever or force people to come up with solutions to whether /usr/bin/python == python2 or python3 right now while it's fresh and relevant in their minds. -Toshio signature.asc Description: OpenPGP digital signature ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
On 19 Apr 2009, at 02:17, Stephen J. Turnbull wrote: Nick Coghlan writes: 3. Change the shebang lines in Python standard library scripts to be version specific and update release.py to fix them all when bumping the version number in the source tree. +1 I think that it's probably best to leave python, python2, and python3 for the use of downstream distributors. ISTR that was what Guido concluded, in the discuss that led to Python 3 defaulting to altinstall---it wasn't just convenient because Python 3 is a major change, but that experience has shown that deciding which Python is going to be The python on somebody's system just isn't a decision that Python should make. Ok, so if I understand, the situation is: * python points to 2.x version * python3 points to 3.x version * need to be able to run certain 3k scripts from cmdline (since we're talking about shebangs) using Python3k even though python points to 2.x So, if I got the situation right, then do these same scripts understand that PYTHONPATH and PYTHONHOME and all the others are also probably pointing to 2.x code? Jared ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Jared Grubb wrote: On 19 Apr 2009, at 02:17, Stephen J. Turnbull wrote: Nick Coghlan writes: 3. Change the shebang lines in Python standard library scripts to be version specific and update release.py to fix them all when bumping the version number in the source tree. +1 I think that it's probably best to leave python, python2, and python3 for the use of downstream distributors. ISTR that was what Guido concluded, in the discuss that led to Python 3 defaulting to altinstall---it wasn't just convenient because Python 3 is a major change, but that experience has shown that deciding which Python is going to be The python on somebody's system just isn't a decision that Python should make. Ok, so if I understand, the situation is: * python points to 2.x version * python3 points to 3.x version * need to be able to run certain 3k scripts from cmdline (since we're talking about shebangs) using Python3k even though python points to 2.x So, if I got the situation right, then do these same scripts understand that PYTHONPATH and PYTHONHOME and all the others are also probably pointing to 2.x code? IIRC the proposal was to also create PYTHON3PATH and PYTHON3HOME. Michael Jared ___ 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/fuzzyman%40voidspace.org.uk -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
On Sun, Apr 19, 2009 at 05:51, Steven Bethard steven.beth...@gmail.com wrote: That's an unfortunate decision. When the 2.X line stops being maintained (after 2.7 maybe?) we're going to be stuck with the 3 suffix forever for the real Python. Yes, but that's the only decision that really works. Why doesn't it make more sense to just use python3 only for altinstall and python for fullinstall? Because you will then get Python 3 trying to run all shebangs that should be run with python 2. Making Python 3 default doesn't make it compatible. ;-) And yes, that means we are stuck with it forever, and I don't like that either, but nobody could come up with an alternative. The recommendation to use python3 could change back to use python once 2.7 falls out of support, which is gonna be many years still. And until then we kinda need different shebang lines. Not much you can do to get around that. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Steven Bethard wrote: That's an unfortunate decision. When the 2.X line stops being maintained (after 2.7 maybe?) we're going to be stuck with the 3 suffix forever for the real Python. I don't see why we have to be stuck with it forever. When 2.x has faded into the sunset, we can start aliasing 'python' to 'python3' if we want, can't we? -- Greg ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Nick Coghlan 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). Seems like what we need is something in between altinstall and fullinstall that aliases 'python3' but not 'python', and make that the default. Maybe call it 'install3'. -- Greg ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Nick Coghlan writes: 3. Change the shebang lines in Python standard library scripts to be version specific and update release.py to fix them all when bumping the version number in the source tree. +1 I think that it's probably best to leave python, python2, and python3 for the use of downstream distributors. ISTR that was what Guido concluded, in the discuss that led to Python 3 defaulting to altinstall---it wasn't just convenient because Python 3 is a major change, but that experience has shown that deciding which Python is going to be The python on somebody's system just isn't a decision that Python should make. Sure, the difference between Python 2 and Python 3 is big enough to be a hairy nuisance 95% of the time, while the difference between Python 2.5 and Python 2.6 is so only 5% of the time. But the fact is that incompatibilities arise with a minor version bump, too, and all the major distros that I know about have some way to select the default Python version that will be python. That's not because they want to distinguish between Python 2 and Python 3, nor between Python 2 and Python 1. ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
I think that it's probably best to leave python, python2, and python3 for the use of downstream distributors. ISTR that was what Guido concluded, in the discuss that led to Python 3 defaulting to altinstall---it wasn't just convenient because Python 3 is a major change, but that experience has shown that deciding which Python is going to be The python on somebody's system just isn't a decision that Python should make. Yes. However, at the language summit in Chicago, it was agreed that the installation should also provide a python3 symlink. I don't recall the agreement wrt. to the names of executables on Windows. Regards, Martin ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
2009/4/19 Steven Bethard steven.beth...@gmail.com: On Sat, Apr 18, 2009 at 8:14 PM, Benjamin Peterson benja...@python.org wrote: 2009/4/18 Nick Coghlan ncogh...@gmail.com: I see a few options: 1. Abandon the python name for the 3.x series and commit to calling it python3 now and forever (i.e. actually make the decision that Mitchell refers to). I believe this was decided on sometime (the sprints?). That's an unfortunate decision. When the 2.X line stops being maintained (after 2.7 maybe?) we're going to be stuck with the 3 suffix forever for the real Python. Why doesn't it make more sense to just use python3 only for altinstall and python for fullinstall? Agreed. Personally, I'm -0 on this decision. I'd be -1 if I was a Linux user, or if I thought that it would be applied to Windows as well. As it is, my -0 is based on it doesn't affect me, but it seems wrong to have the official name be different things depending on platform. Paul. ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Martin v. Löwis wrote: I think that it's probably best to leave python, python2, and python3 for the use of downstream distributors. ISTR that was what Guido concluded, in the discuss that led to Python 3 defaulting to altinstall---it wasn't just convenient because Python 3 is a major change, but that experience has shown that deciding which Python is going to be The python on somebody's system just isn't a decision that Python should make. Yes. However, at the language summit in Chicago, it was agreed that the installation should also provide a python3 symlink. I don't recall the agreement wrt. to the names of executables on Windows. The installer still leaves PATH alone by default, doesn't it? That means the Windows version selection is done by naming the directory. Although I guess choosing a file association for .py files becomes rather more interesting... Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Peterson wrote: 2009/4/18 Nick Coghlan ncogh...@gmail.com: Benjamin Peterson wrote: 2009/4/18 Mitchell L Model mlmli...@comcast.net: Some library files, such as pdb.py, begin with #!/usr/bin/env python In various discussions regarding some issues I submitted I was told that the decision had been made to call Python 3.x release executables python3. (One of the conflicts I ran into when I made 'python' a link to python3.1 was that some tools used in making the HTML documentation haven't been upgraded to run with 3.) Shouldn't all library files that begin with the above line be changed so that they read 'python3' instead of python? Perhaps I should have just filed this as an issue, but I'm not confident of the state of the plan to move to python3 as the official executable name. That sounds correct. Please file a bug report. As Kevin pointed out, while this is a problem, changing the affected scripts to say python3 instead isn't the right answer. All that happened with the Python 3 installers is that they do 'altinstall' rather than 'fullinstall' by default, thus leaving the 'python' alias alone. There is no python3 alias unless a user creates it for themselves (or a distro packager does it for them). I've actually implemented a python3 alias for 3.1. I see a few options: 1. Abandon the python name for the 3.x series and commit to calling it python3 now and forever (i.e. actually make the decision that Mitchell refers to). I believe this was decided on sometime (the sprints?). It was at the Language Summit. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ6zg3+gerLs4ltQ4RAt2ZAKDRGXMXBRs5FiHLnC0MQt56janafwCdGytm /nrHCiifI/KibI+ljppr3aA= =uYha -END PGP SIGNATURE- ___ 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
[Python-Dev] #!/usr/bin/env python -- python3 where applicable
Some library files, such as pdb.py, begin with #!/usr/bin/env python In various discussions regarding some issues I submitted I was told that the decision had been made to call Python 3.x release executables python3. (One of the conflicts I ran into when I made 'python' a link to python3.1 was that some tools used in making the HTML documentation haven't been upgraded to run with 3.) Shouldn't all library files that begin with the above line be changed so that they read 'python3' instead of python? Perhaps I should have just filed this as an issue, but I'm not confident of the state of the plan to move to python3 as the official executable name. ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
2009/4/18 Mitchell L Model mlmli...@comcast.net: Some library files, such as pdb.py, begin with #!/usr/bin/env python In various discussions regarding some issues I submitted I was told that the decision had been made to call Python 3.x release executables python3. (One of the conflicts I ran into when I made 'python' a link to python3.1 was that some tools used in making the HTML documentation haven't been upgraded to run with 3.) Shouldn't all library files that begin with the above line be changed so that they read 'python3' instead of python? Perhaps I should have just filed this as an issue, but I'm not confident of the state of the plan to move to python3 as the official executable name. That sounds correct. Please file a bug report. -- Regards, Benjamin ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
On Apr 18, 2009, at 1:08 PM, Mitchell L Model wrote: Some library files, such as pdb.py, begin with #!/usr/bin/env python In various discussions regarding some issues I submitted I was told that the decision had been made to call Python 3.x release executables python3. (One of the conflicts I ran into when I made 'python' a link to python3.1 was that some tools used in making the HTML documentation haven't been upgraded to run with 3.) Shouldn't all library files that begin with the above line be changed so that they read 'python3' instead of python? Perhaps I should have just filed this as an issue, but I'm not confident of the state of the plan to move to python3 as the official executable name. Hrmm ... On installing from source, one either gets: ./bin/python3.0 Or is using 'make fullinstall': ./bin/python So the default and the tutorial (http://docs.python.org/3.0/tutorial/interpreter.html ) refer to 'python3.0'. But I've done all my Python installs with 'make fullinstall' and then just manage my environment such that 'python' points to a 2.x or 3.x release depending upon what the source code I'm working on requires. If using something such as the Mac OS X Installer you'll get both a 'python' and 'python3.0'. Are there some Python installers that provide './bin/python3'? But if there sometimes just 'python', 'python3.0' or 'python3' then it's not possible for the shebang to work with both all known install methods ... One could argue that executable files part of the python standard library should have their interpreter hard-coded to the python interpreter to which they are installed with, e.g.: #!/Users/kteague/shared/python-3.0.1/bin/python Of course, this would remove the ability for a Python installation to be re-located ... if you wanted to move the install, you'd need to re- install it in order to maintain the proper shebangs. But it would mean that these scripts would also use the correct interpreter regardless of a user's current environemnt. Or, if the standard library was packaged such that all of it's scripts were advertised as console_scripts in the entry_points, it'd be easier for different install approaches to decide how to write out the shebang or to instead provide wrapper scripts for accessing those entry points (since it might be nice to have a ./bin/pdb). But that's a bit pie-in-the-sky since entry_points isn't even yet a part of the Distutils Metadata. ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Benjamin Peterson wrote: 2009/4/18 Mitchell L Model mlmli...@comcast.net: Some library files, such as pdb.py, begin with #!/usr/bin/env python In various discussions regarding some issues I submitted I was told that the decision had been made to call Python 3.x release executables python3. (One of the conflicts I ran into when I made 'python' a link to python3.1 was that some tools used in making the HTML documentation haven't been upgraded to run with 3.) Shouldn't all library files that begin with the above line be changed so that they read 'python3' instead of python? Perhaps I should have just filed this as an issue, but I'm not confident of the state of the plan to move to python3 as the official executable name. That sounds correct. Please file a bug report. As Kevin pointed out, while this is a problem, changing the affected scripts to say python3 instead isn't the right answer. All that happened with the Python 3 installers is that they do 'altinstall' rather than 'fullinstall' by default, thus leaving the 'python' alias alone. There is no python3 alias unless a user creates it for themselves (or a distro packager does it for them). I see a few options: 1. Abandon the python name for the 3.x series and commit to calling it python3 now and forever (i.e. actually make the decision that Mitchell refers to). 2. Remove the offending shebang lines from the affected files and tell people to use python -m module instead. 3. Change the shebang lines in Python standard library scripts to be version specific and update release.py to fix them all when bumping the version number in the source tree. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Benjamin Peterson wrote: 2009/4/18 Nick Coghlan ncogh...@gmail.com: I see a few options: 1. Abandon the python name for the 3.x series and commit to calling it python3 now and forever (i.e. actually make the decision that Mitchell refers to). I believe this was decided on sometime (the sprints?). If that decision has already been made, then sure, changing the shebang lines to use the new name is the right thing to do. It certainly wouldn't be the first time something was discussed at Pycon or the sprints and those involved forgot to mention the outcome on the list :) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
At 20:51 -0700 04/18/2009, Steven Bethard wrote: On Sat, Apr 18, 2009 at 8:14 PM, Benjamin Peterson benja...@python.org wrote: 2009/4/18 Nick Coghlan ncogh...@gmail.com: I see a few options: 1. Abandon the python name for the 3.x series and commit to calling it python3 now and forever (i.e. actually make the decision that Mitchell refers to). I believe this was decided on sometime (the sprints?). That's an unfortunate decision. When the 2.X line stops being maintained (after 2.7 maybe?) we're going to be stuck with the 3 suffix forever for the real Python. Why doesn't it make more sense to just use python3 only for altinstall and python for fullinstall? Just use python3 in the shebang lines all the time (where applicable ;), as it is made by both altinstall and fullinstall. fullinstall also make plain python, but that is not important. -- TonyN.:' mailto:tonynel...@georgeanelson.com ' http://www.georgeanelson.com/ ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Steven Bethard wrote: On Sat, Apr 18, 2009 at 8:14 PM, Benjamin Peterson benja...@python.org wrote: 2009/4/18 Nick Coghlan ncogh...@gmail.com: I see a few options: 1. Abandon the python name for the 3.x series and commit to calling it python3 now and forever (i.e. actually make the decision that Mitchell refers to). I believe this was decided on sometime (the sprints?). That's an unfortunate decision. When the 2.X line stops being maintained (after 2.7 maybe?) we're going to be stuck with the 3 suffix forever for the real Python. Why doesn't it make more sense to just use python3 only for altinstall and python for fullinstall? 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). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
On Sat, Apr 18, 2009 at 9:37 PM, Nick Coghlan ncogh...@gmail.com wrote: Steven Bethard wrote: On Sat, Apr 18, 2009 at 8:14 PM, Benjamin Peterson benja...@python.org wrote: 2009/4/18 Nick Coghlan ncogh...@gmail.com: I see a few options: 1. Abandon the python name for the 3.x series and commit to calling it python3 now and forever (i.e. actually make the decision that Mitchell refers to). I believe this was decided on sometime (the sprints?). That's an unfortunate decision. When the 2.X line stops being maintained (after 2.7 maybe?) we're going to be stuck with the 3 suffix forever for the real Python. Why doesn't it make more sense to just use python3 only for altinstall and python for fullinstall? 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. 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
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 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 Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Nick Coghlan 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 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 Adjusting the python2 installs to do something similar with symlinks to python2 would also be useful when python3 becomes the standard python and python2 is used for legacy. I.e. 2.x altinstall: - installs python2.x executable 2.x py2install (default for make install): - installs python2.x executable - adjusts (or creates) python2 symlink to new executable 2.x fullinstall (default for make install): - installs python2.x executable - adjusts (or creates) python2 symlink to new executable - adjusts (or creates) python symlink to new executable Allan ___ 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
Re: [Python-Dev] #!/usr/bin/env python -- python3 where applicable
Allan McRae wrote: Nick Coghlan 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 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 Adjusting the python2 installs to do something similar with symlinks to python2 would also be useful when python3 becomes the standard python and python2 is used for legacy. I.e. 2.x altinstall: - installs python2.x executable 2.x py2install (default for make install): And of course that was supposed to say future default... - installs python2.x executable - adjusts (or creates) python2 symlink to new executable 2.x fullinstall (default for make install): - installs python2.x executable - adjusts (or creates) python2 symlink to new executable - adjusts (or creates) python symlink to new executable ___ 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
