Tim Golden m...@timgolden.me.uk added the comment:
Effectively made redundant by PEP 397, implemented in 3.3
--
resolution: - wont fix
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Mark Lawrence breamore...@yahoo.co.uk added the comment:
Hum, I think I spoke too soon. @Brian: @Tim: what do you think about this?
--
nosy: +brian.curtin, tim.golden
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4485
Brian Curtin cur...@acm.org added the comment:
msg77014 could bring startup time down significantly so I'm -1 on that.
Overall I've never found difficulty in running scripts with the right version
so I don't have a strong enough opinion on any of it. I think it's probably
something which
Mark Lawrence breamore...@yahoo.co.uk added the comment:
Right now this would suit me down to the ground, as I'm running four
maintenance versions, 2.6/7 and 3.1/2 in parallel. But as this is a feature
request it will not happen until 3.2 at the earliest.
--
nosy: +BreamoreBoy
Andreas Lemke mueslifl...@nexgo.de added the comment:
Python 2.5, 2.6, 3.0, etc. are not fully compatible programming languages. And
we cannot expect that there will ever be the one and only ultimate version of
Python (hopefully). Many of us need to have more than one of them installed
Changes by Matthieu Labbé bugs.python@mattlabbe.com:
--
nosy: +matthieu.labbe
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4485
___
___
Daniel Harding dhard...@gmail.com added the comment:
I have created a script that does essentially what Mark Tolonen
suggests. When it is provided a script to run, it looks for a #! line
and if it exists, attempts to use that to determine which version of
python.exe to use. It also has the
Changes by Daniel Harding dhard...@gmail.com:
--
nosy: +dharding
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4485
___
___
Python-bugs-list
Mark Tolonen [EMAIL PROTECTED] added the comment:
An extension to this idea: Support parsing #! lines in Windows and
select the version of Python used. python.exe could examine:
#!/usr/bin/python30
pattern match python##, look in the registry to see if that version
of python is installed,
Glenn Linderman [EMAIL PROTECTED] added the comment:
Since Python hasn't done that until now, it won't help much with the
transition from 2to3. The earliest versions that could add that would
be 3.1 and 2.7, it would seem, as it is a new fetaure. Perhaps it would
be worth doing, in planning
Mark Tolonen [EMAIL PROTECTED] added the comment:
I see it as primarily useful in this transition period between 2.x and
3.0, since py3 scripts aren't backward compatible and I see both being
installed for the few years. It could be a front-end launcher
suitable for ftype Python.File that
Glenn Linderman [EMAIL PROTECTED] added the comment:
Ah yes, it could work as a front-end launcher, since # is a comment
character for Python anyway, so all Pythons would ignore such a line.
So that can be done completely independently of python itself, and
installed separately, and used by
New submission from Glenn Linderman [EMAIL PROTECTED]:
Here's how I set up my computer, for multiple versions. Now to change
the default, I just use the assoc command to change the association
for .py to one of the three listed ftypes. Simple and quick.
c:\ftype Python25.File
ftype
13 matches
Mail list logo
