On Fri, Mar 4, 2011 at 16:04, Glenn Linderman <v+python@g.nevcal.com> wrote:
Sadly, there seems to be strong resistance to the idea of putting the Python install directory on the Windows path, of course, without some additional solutions (python2.exe, python3.exe, etc.), that doesn't help the multi-version install, only the single version install.
FWIW, I plan on spending time on the PATH issue for 3.3. It seems like much of the resistance could be quelled with actual code. It would be _nice_, but harder, and harder to get consensus on, to write a
little "python launcher" (in a compiled language, not Python, as that would double the startup time) to do some grunge on Windows. Some possibilities, not all would be needed. <SNIP>
* Could also add .py24, .py31, or even .py262, .py301, etc., assoc and
ftype, depending on how many versions of Windows Python are installed.
-INF