March 4, 2011
5:41 p.m.
On Fri, 2011-03-04 at 22:21 +0100, "Martin v. Löwis" wrote:
As for Windows support: we currently don't install a python3.exe binary, let alone python2.exe or pythonw2.exe (or is that python2w.exe?). I'll adjust the installer if the PEP asks me to. For the reasons discussed, I'm -0 on the change (i.e. double-clicking .py will continue to launch the most-recently installed Python, rather than the "right" one, and setting PYTHONPATH will continue to break installations).
I think the python2.exe or python3.exe (or both) for Windows would be a good idea. I also think we need to seriously consider fixing the double-click action for Windows. .py2 and .py3 extensions could work, but seems clumsy.