<div class="gmail_quote">On Fri, Mar 4, 2011 at 16:04, Glenn Linderman <span dir="ltr"><<a href="mailto:v%2Bpython@g.nevcal.com">v+python@g.nevcal.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div text="#330033" bgcolor="#ffffff">
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.<br></div></blockquote><div><br></div><div>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.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div text="#330033" bgcolor="#ffffff">
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.<br><SNIP></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div text="#330033" bgcolor="#ffffff">
* Could also add .py24, .py31, or even .py262, .py301, etc., assoc
and ftype, depending on how many versions of Windows Python are
installed.<br></div></blockquote><div><br></div><div>-INF</div></div>