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
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 p
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 l
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
> The installer still leaves PATH alone by default, doesn't it?
Correct. However, people frequently set the path "by hand", so
they would probably appreciate a python3 binary (and pythonw3?
python3w?). Of course, those people could also manually
copy/rename the executable.
> Although I guess cho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin Peterson wrote:
> 2009/4/18 Nick Coghlan :
>> Benjamin Peterson wrote:
>>> 2009/4/18 Mitchell L Model :
Some library files, such as pdb.py, begin with
#!/usr/bin/env python
In various discussions regarding some issues I s
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
2009/4/19 Steven Bethard :
> On Sat, Apr 18, 2009 at 8:14 PM, Benjamin Peterson
> wrote:
>> 2009/4/18 Nick Coghlan :
>>> 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
>
> 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 ex
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
In article <49eab0c2.8040...@gmail.com>,
Nick Coghlan wrote:
> Steven Bethard wrote:
> > On Sat, Apr 18, 2009 at 9:37 PM, 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
>
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
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
ali
On Sun, Apr 19, 2009 at 05:51, 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.
Yes, but that's the only decision that really works.
> Why doesn't it
Allan McRae wrote:
Nick Coghlan wrote:
Steven Bethard wrote:
On Sat, Apr 18, 2009 at 9:37 PM, 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
Nick Coghlan wrote:
Steven Bethard wrote:
On Sat, Apr 18, 2009 at 9:37 PM, 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
On Sat, Apr 18, 2009 at 10:04 PM, Nick Coghlan wrote:
> Steven Bethard wrote:
>> On Sat, Apr 18, 2009 at 9:37 PM, 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
Steven Bethard wrote:
> On Sat, Apr 18, 2009 at 9:37 PM, 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.
On Sat, Apr 18, 2009 at 9:37 PM, Nick Coghlan wrote:
> Steven Bethard wrote:
>> On Sat, Apr 18, 2009 at 8:14 PM, Benjamin Peterson
>> wrote:
>>> 2009/4/18 Nick Coghlan :
I see a few options:
1. Abandon the "python" name for the 3.x series and commit to calling it
"python3" now and
Steven Bethard wrote:
> On Sat, Apr 18, 2009 at 8:14 PM, Benjamin Peterson
> wrote:
>> 2009/4/18 Nick Coghlan :
>>> 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
>>> re
At 20:51 -0700 04/18/2009, Steven Bethard wrote:
>On Sat, Apr 18, 2009 at 8:14 PM, Benjamin Peterson
>wrote:
>> 2009/4/18 Nick Coghlan :
>>> 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 decis
On Sat, Apr 18, 2009 at 8:14 PM, Benjamin Peterson wrote:
> 2009/4/18 Nick Coghlan :
>> 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
Benjamin Peterson wrote:
> 2009/4/18 Nick Coghlan :
>> 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
2009/4/18 Nick Coghlan :
> Benjamin Peterson wrote:
>> 2009/4/18 Mitchell L Model :
>>> 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 rele
Benjamin Peterson wrote:
> 2009/4/18 Mitchell L Model :
>> 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
>>
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 co
2009/4/18 Mitchell L Model :
> 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 whe
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 python
28 matches
Mail list logo
