mirror of https://github.com/python/cpython
445ad997ab
As stated in PEP 11, 3.4 removes code on Windows platforms where COMSPEC points to command.com. The w9xpopen project in Visual Studio was added to support that case, and there was a special case in subprocess to cover that situation. This change removes the w9xpopen project from the Visual Studio solution and removes any references to the w9xpopen executable. |
||
|---|---|---|
| .. | ||
| README.txt | ||
| crtlicense.txt | ||
| msi.py | ||
| msilib.py | ||
| msisupport.c | ||
| msisupport.mak | ||
| schema.py | ||
| sequence.py | ||
| uisample.py | ||
README.txt
Packaging Python as a Microsoft Installer Package (MSI) ======================================================= Using this library, Python can be packaged as a MS-Windows MSI file. To generate an installer package, you need a build tree. By default, the build tree root directory is assumed to be in "../..". This location can be changed by adding a file config.py; see the beginning of msi.py for additional customization options. The packaging process assumes that binaries have been generated according to the instructions in PCBuild/README.txt, and that you have either Visual Studio or the Platform SDK installed. In addition, you need the Python COM extensions, either from PythonWin, or from ActivePython. To invoke the script, open a cmd.exe window which has cabarc.exe in its PATH (e.g. "Visual Studio .NET 2003 Command Prompt"). Then invoke <path-to-python.exe> msi.py If everything succeeds, pythonX.Y.Z.msi is generated in the current directory.