On Sunday, March 6, 2011 at 9:53 AM, Brian Curtin wrote: > On Sun, Mar 6, 2011 at 11:41, Michael Foord <fuzzy...@voidspace.org.uk> wrote: > - Hide quoted message - > > I would like to see us create version specific (i.e. python32.exe / > > python32w.exe) binaries (or links if we drop support for earlier versions > > of Windows or some filesystems - I'm agnostic on that issue) *plus* a > > python3.exe / python3w.exe with "last install wins" (as it is for currently > > for file associations). > > > > I don't have an ActiveState install on this machine, but I know they have > been adding some form of version specific binaries for a while, so maybe they > can comment on what they chose and how they chose it, and how people are > using it. Are Sridhar or Trent on here? > ActivePython for Windows includes the following binaries on Windows:
* python.exe * python3.2.exe * python3.xe (plus the `pythonw` versions) python3.2.exe is better than python32.exe because that matches the invocation (eg: "python3.2 -m foo") on Unix. Similarly for 2.x (python2.exe / python2.7.exe). All of this is particularly useful if the installer adds Python directory to %PATH% (which is the case for ActivePython, but not the one from python.org). -srid
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
