windows: remove Scripts/pip*.exe from distributions

These executables didn't work because of the way they are compiled
references the absolute path of python.dll on the build machine.
This is probably fixable. But for now we go the easy route of
deleting the files.

Closes #88.

Author: indygreg

cpython-windows/build.py

@@ -2154,6 +2154,21 @@ def build_cpython(
             os.environ,
         )
 
+        # The executables in the Scripts/ directory don't work because they reference
+        # python.dll in the wrong path. You can run these via e.g. `python.exe -m pip`.
+        # So just delete them for now.
+        for filename in sorted(os.listdir(install_dir / "Scripts")):
+            assert filename.startswith("pip") and filename.endswith(".exe")
+            p = install_dir / "Scripts" / filename
+            log("removing non-functional executable: %s" % p)
+            os.unlink(p)
+
+        # But this leaves the Scripts directory empty, which we don't want. So
+        # create a placeholder file to ensure the directory is created on archive
+        # extract.
+        with (install_dir / "Scripts" / ".empty").open("ab"):
+            pass
+
         # Now copy the build artifacts into the output directory.
         build_info = collect_python_build_artifacts(
             pcbuild_path,

docs/quirks.rst

@@ -143,6 +143,20 @@ run time, the ``TCL_LIBRARY`` environment variable is set from within
 the process before the Python interpreter is initialized. This ensures the
 ``.tcl`` files from the Python distribution are used.
 
+.. _quirk_windows_no_pip:
+
+No ``pip.exe`` on Windows
+=========================
+
+The Windows distributions have ``pip`` installed however no ``Scripts/pip.exe``,
+``Scripts/pip3.exe``, and ``Scripts/pipX.Y.exe`` files are provided because
+the way these executables are built isn't portable. (It might be possible to
+change how these are built to make them portable.)
+
+To use pip, run ``python.exe -m pip``. (It is generally a best practice to
+invoke pip via ``python -m pip`` on all platforms so you can be explicit
+about the ``python`` executable that pip uses.)
+
 .. _quirk_macos_linking:
 
 Linking Static Library on macOS