Lines Matching +full:build +full:- +full:with +full:- +full:python
1 Quick Build Info
4 For testing, the installer should be built with the Tools/msi/build.bat
7 build.bat [-x86] [-x64] [-ARM64] [--doc]
9 For an official release, the installer should be built with the
12 set PYTHON=<path to Python 3.8 or later>
13 set SPHINXBUILD=<path to sphinx-build.exe>
16 buildrelease.bat [-x86] [-x64] [-ARM64] [-D] [-B]
17 [-o <output directory>] [-c <certificate name>]
24 Python is distributed on Windows as an installer that will configure the
25 user's system. This allows users to have a functioning copy of Python
26 without having to build it themselves.
33 * add entry points for modifying, repairing and uninstalling Python
34 * make it easy to launch Python, its documentation, and IDLE
45 and command-line logic, as well as the ability to locate and optionally
49 of Python. These MSIs should not be launched directly by users. MSIs can
52 Each CAB contains the files making up a Python installation. CABs are
64 Before building the installer, download extra build dependencies using
76 For testing, the installer should be built with the Tools/msi/build.bat
79 build.bat [-x86] [-x64] [-ARM64] [--doc] [--test-marker] [--pack]
81 This script will build the required configurations of Python and
82 generate an installer layout in PCbuild/(win32|amd64)/en-us.
84 Specify -x86, -x64 and/or -ARM64 to build for each platform. If none are
86 release versions of Python are required for the installer.
88 Specify --doc to include the documentation files. Ensure %PYTHON% and
91 Specify --test-marker to build an installer that works side-by-side with
92 an official Python release. All registry keys and install locations will
96 Specify --pack to build an installer that does not require all MSIs to
100 For an official release, the installer should be built with the
103 set PYTHON=<path to Python 2.7 or 3.4>
104 set SPHINXBUILD=<path to sphinx-build.exe>
107 buildrelease.bat [-x86] [-x64] [-ARM64] [-D] [-B]
108 [-o <output directory>] [-c <certificate name>]
110 Specify -x86, -x64 and/or -ARM64 to build for each platform. If none are
112 release versions of Python are required for the installer.
114 Specify -D to skip rebuilding the documentation. The documentation is
115 required for a release and the build will fail if it is not available.
116 Ensure %PYTHON% and %SPHINXBUILD% are set if you omit this option.
118 Specify -B to skip rebuilding Python. This is useful to only rebuild the
121 Specify -o to set an output directory. The installer layouts will be
122 copied to platform-specific subdirectories of this path.
124 Specify -c to choose a code-signing certificate to be used for all the
125 signable binaries in Python as well as each file making up the
126 installer. Official releases of Python must be signed.
132 To manually build layouts of the installer, build one of the projects in
157 Used to generate unique IDs for the installers to allow side-by-side
158 installation. Forks of Python can use the same installer infrastructure
162 Official releases use https://www.python.org/(architecture name)
166 can be downloaded from. The build version and architecture will be
178 Specifies the certificate to sign the installer layout with. If omitted,
195 path or have run get_externals.bat. You may also need to "gpg2.exe --import"
198 uploadrelease.bat --host <host> --user <username> [--dry-run] [--no-gpg]
206 Use --dry-run to display the generated upload commands without executing
208 --no-gpg is also passed.
210 Use --no-gpg to suppress signature generation and upload.
213 correct for official Python releases, but may be overridden with
214 --target <path> for other purposes. This path should generally not include
224 --------
227 directory). The project file is a .wixproj and the build output is a
228 single MSI. Packages are built with the WiX Toolset. Some project files
253 All packages are built with the Tools/msi/common.wxs file, and so any
276 The .wxl_template file is specially handled by the build system for this
282 ------
285 will represent the Python installer. It is built from Tools/msi/bundle
286 with packages references in Tools/msi/bundle/packagegroups.
288 Build logic for the bundle is in bundle.targets, but should be invoked
299 packages require two separate entries to support both per-user and
300 all-users installations. Because these reuse the same package, it does
317 omitted. This makes them suitable for pre- or post-install tasks that
321 ---------------------
334 There are two installation layouts for Python on Windows, with the only
340 "%ProgramFiles%\Python3X" for the 64-bit interpreter and
341 "%ProgramFiles(x86)%\Python3X-32" for the 32-bit interpreter. (Note that
342 the latter path is equivalent to "%ProgramFiles%\Python3X-32" when
343 running a 32-bit version of Windows.) This location requires
347 is "%LocalAppData%\Programs\Python\Python3X" for the 64-bit interpreter
348 and "%LocalAppData%\Programs\Python\Python3X-32" for the 32-bit
351 of Python's files.
357 .\python[w].exe The core executable files
372 available on PATH. (See Launching Python below.) For the current user,
373 they are installed in "%LocalAppData%\Programs\Python\PyLauncher".
382 can locate and identify installations of Python. The locations of these
385 For 64-bit interpreters installed for all users, the root key is:
386 HKEY_LOCAL_MACHINE\Software\Python\PythonCore\3.X
388 For 32-bit interpreters installed for all users on a 64-bit operating
390 HKEY_LOCAL_MACHINE\Software\Wow6432Node\Python\PythonCore\3.X-32
392 For 32-bit interpreters installed for all users on a 32-bit operating
394 HKEY_LOCAL_MACHINE\Software\Python\PythonCore\3.X-32
396 For 64-bit interpreters installed for the current user:
397 HKEY_CURRENT_USER\Software\Python\PythonCore\3.X
399 For 32-bit interpreters installed for the current user:
400 HKEY_CURRENT_USER\Software\Python\PythonCore\3.X-32
402 When the core Python executables are installed, a key "InstallPath" is
403 created within the root key with its default value set to the
405 with the full path to the main Python interpreter, and a key
406 "InstallGroup" is created with its default value set to the product
407 name "Python 3.X".
409 When the Python standard library is installed, a key "PythonPath" is
410 created within the root key with its default value set to the full path
415 root key, with a subkey "Main Python Documentation" with its default
419 The py.exe launcher is installed as part of a regular Python install,
421 versions of Python. As a result, it has different root keys for its
424 When installed for all users on a 64-bit operating system, the
426 HKEY_LOCAL_MACHINE\Software\Wow6432Node\Python\Launcher
428 When installed for all users on a 32-bit operating system, the
430 HKEY_LOCAL_MACHINE\Software\Python\Launcher
433 HKEY_CURRENT_USER\Software\Python\Launcher
436 its root key with its default value set to the launcher's install
440 Launching Python
444 installed, a folder "Python 3.X" is created. Every shortcut should be
449 The core Python executables creates a shortcut "Python 3.X (32-bit)" or
450 "Python 3.X (64-bit)" depending on the interpreter.
452 The documentation creates a shortcut "Python 3.X 32-bit Manuals" or
453 "Python 3.X 64-bit Manuals". The documentation is identical for all
457 Installing IDLE creates a shortcut "IDLE (Python 3.X 32-bit)" or "IDLE
458 (Python 3.X 64-bit)" depending on the interpreter.
461 For users who often launch Python from a Command Prompt, an option is
462 provided to add the directory containing python.exe to the user or
465 for an all users install and the user PATH for a per-user install.
467 When the user only has one version of Python installed, this will behave
469 the user PATH, users cannot override a system-wide installation of
470 Python on their PATH. Further, because the installer can only prepend to
471 the path, later installations of Python will take precedence over
477 preferred order. System-wide installations of Python should consider not
483 sensible search order for Python installations. User installations are
484 preferred over system-wide installs, and later versions are preferred
485 regardless of installation order (with the exception that py.exe
486 currently prefers 2.x versions over 3.x versions without the -3 command
489 For both 32-bit and 64-bit interpreters, the 32-bit version of the
491 consistent (as the 64-bit launcher is subtly different from the 32-bit
493 versions of Python will upgrade the launcher in-place, using Windows
494 Installer's upgrade functionality to avoid conflicts with earlier
498 files to launch with py.exe and .pyw files to launch with pyw.exe. This
499 makes Python files respect shebang lines by default and also avoids
500 conflicts between multiple Python installations.
506 After installation, Python may be modified, repaired or uninstalled by
522 Removing Python will clean up all the files and registry keys that were
524 explicitly handled by the installer. Python packages installed later