Lines Matching full:launcher

72   C Runtime Library is required or you install the :ref:`launcher` for all
75 * The :ref:`launcher` will be installed according to the option at the bottom
77 * The standard library, test suite, launcher and pip will be installed
90 * The :ref:`launcher` will be installed into the Windows directory
163 |                           | launcher is also installed.          |                          |
185 | Include_launcher          | Install :ref:`launcher`.             | 1                        |
187 | InstallLauncherAllUsers   | Installs :ref:`launcher` for all     | 1                        |
203 | LauncherOnly              | Only installs the launcher. This     | 0                        |
224 (Note that omitting the launcher also omits file associations, and is only
226 that included the launcher.)
284 :ref:`launcher`, which has its own entry in Programs and Features.
326 The ``py.exe`` launcher will detect this Python installation, but will prefer
449 Using a specialized executable as a launcher requires some coding, but provides
450 the most transparent experience for users. With a customized launcher, there are
453 associations behave properly. In most cases, a custom launcher should simply be
464 specialized launcher, packages can be located in other locations as there is an
517 versions of Python, consider using the :ref:`launcher`.
648 Python Launcher for Windows
653 The Python launcher for Windows is a utility which aids in locating and
658 Unlike the :envvar:`PATH` variable, the launcher will correctly select the most
663 The launcher was originally specified in :pep:`397`.
673 System-wide installations of Python 3.3 and later will put the launcher on your
674 :envvar:`PATH`. The launcher is compatible with all available versions of
676 launcher is available, execute the following command in Command Prompt:
703 If you see the following error, you do not have the launcher installed:
710 Per-user installations of Python do not add the launcher to :envvar:`PATH`
718 If the launcher is run with no explicit Python version specification, and a
720 the external ``virtualenv`` tool) active, the launcher will run the virtual
764 The launcher should have been associated with Python files (i.e. ``.py``,
766 when you double-click on one of these files from Windows explorer the launcher
770 The key benefit of this is that a single launcher can support multiple Python
779 how a script should be executed.  This launcher allows the same facilities to
784 Windows, this launcher supports a number of 'virtual' commands to specify
800 be used by the launcher without modification.  If you are writing a new script
812    Beginning with python launcher 3.7 it is possible to request 64-bit version
839 Two .ini files will be searched by the launcher - ``py.ini`` in the current
842 same directory as the launcher. The same .ini files are used for both the
843 'console' version of the launcher (i.e. py.exe) and for the 'windows' version
848 .ini file next to the launcher, can override commands in that global .ini file.
867 available with the launcher included with Python 3.7 or newer.)
872 is found, the launcher will enumerate the installed Python versions and use
880 launcher - a 32-bit launcher will prefer to execute a 64-bit Python installation
881 of the specified version if available. This is so the behavior of the launcher
884 whether a 32 or 64-bit version of Python and corresponding launcher was
909 in the .INI file used by the launcher.  The section in the INI file is
937 launcher will print diagnostic information to stderr (i.e. to the console).