Specify that the \Windows copy of the launcher is always a 32-bit executable.

pep-0397.txt

@@ -1,7 +1,7 @@
 PEP: 397
 Title: Python launcher for Windows
-Version: $Revision$
-Last-Modified: $Date$
+Version: $Revision: a57419aee37d $
+Last-Modified: $Date: 2012/06/19 15:13:49 $
 Author: Mark Hammond <mhammond@skippinet.com.au>,
         Martin v. Löwis <martin@v.loewis.de>
 Status: Draft
@@ -89,7 +89,11 @@ Installation
     The launcher is installed into the Windows directory (see
     discussion below) if installed by a privileged user. The
     stand-alone installer asks for an alternative location of the
-    installer, and adds that location to the user's PATH.
+    installer, and adds that location to the user's PATH. 
+
+    The installation in the Windows directory is a 32-bit executable
+    (see discussion); the standalone installer may also offer to install
+    64-bit versions of the launcher.
 
     The launcher installation is registered in
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CurrentVersion\SharedDLLs
@@ -101,9 +105,6 @@ Installation
     a release level of 0x10 in FIELD3 of the CPython release on which
     they are based.
 
-    The 32-bit distribution of Python will not install a 32-bit
-    version of the launcher on a 64-bit system.
-
     Once installed, the "console" version of the launcher is
     associated with .py files and the "windows" version associated with .pyw
     files.
@@ -348,6 +349,10 @@ Discussion
     running on a 64-bit system. However, the Windows directory is
     always on the path.
 
+    The launcher that is installed into the Windows directory is a 32-bit
+    executable so that the 32-bit CPython installer can provide the same
+    binary for both 32-bit and 64-bit Windows installations.
+
     Ideally, the launcher process would execute Python directly inside
     the same process, primarily so the parent of the launcher process could
     terminate the launcher and have the Python interpreter terminate.  If the