[New-bugs-announce] [issue4485] fast swap of "default" Windows python versions
report at bugs.python.org
Tue Dec 2 09:51:59 CET 2008
New submission from Glenn Linderman <v+python at g.nevcal.com>:
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.
Python25.File="C:\Python25\python.exe" "%1" %*
Python26.File="C:\Python26\python.exe" "%1" %*
Python30.File="C:\Python30\python.exe" "%1" %*
It would be nice if the ftypes were version specific as created by the
installer; IIRC, I created the above three from the ftype Python.File as
I installed each version.
The Python.File could still be created by default, and could still
reflect the last temporally installed version of Python... but by
documenting the version specific ftypes, the user could still switch
I suppose there is a question of if the version should contain two or
three parts, i.e. Python253.File; and if the version should be separated
such as Python2.5.3.File; the above worked for me for the moment, but
some thought might reveal a more useful technique.
It might even be appropriate for a Python version to create 3 ftypes,
such that version N.M.O creates ftypes named PythonN.File,
PythonN.M.File, and PythonN.M.O.File. All but the most specific one
would be subject to change when additional versions are installed. If M
or O are zero, they should probably still be specified (as zero) in a
scheme like this, so that there would be a solid way of referring to all
the specific versions.
title: fast swap of "default" Windows python versions
type: feature request
versions: Python 2.6, Python 3.0
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce