On 05/03/2011 14:22, Nick Coghlan wrote:
[snip...]
Martin has also indicated that making appropriate changes to the Windows installer would not be difficult if we agree that changing the 2.7 maintenance branch in this way is appropriate. True, it's only the more exotic ideas (like trying to do something about the PYTHON* variables or file associations) that become an issue.
Simply supporting having a python3 version and a python2 version on PATH at the same time could work by duplicating the main executables (using "python2w" and "python3w" for the non-console variants), with the sysadmin effectively choosing the preferred version of the installed versions based on the directory order in PATH. Yes. I would also like to see python27.exe and python32.exe (etc) but
Right. But those are issues *anyway* and are orthogonal to this particular one. (And in the case of PYTHON* environment variables not restricted to windows and not addressed by this PEP for any platform.) that may be a step too far (although Martin was open to it we'll have to see what final agreement we come to). All the best, Michael
Cheers, Nick.
-- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html