From 362e61a22d6a4b39152bbd3134dc59cdf73e0903 Mon Sep 17 00:00:00 2001 From: Steve Dower Date: Mon, 16 Jan 2023 16:22:49 +0000 Subject: [PATCH] gh-100247: Improve documentation for custom shebang commands in py.exe launcher --- Doc/using/windows.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Doc/using/windows.rst b/Doc/using/windows.rst index 69bca4d7bd307c..b2a0214026e48c 100644 --- a/Doc/using/windows.rst +++ b/Doc/using/windows.rst @@ -880,14 +880,15 @@ The environment variable :envvar:`PYLAUNCHER_NO_SEARCH_PATH` may be set Shebang lines that do not match any of these patterns are looked up in the ``[commands]`` section of the launcher's :ref:`.INI file `. This may be used to handle certain commands in a way that makes sense for your -system. The name of the command must be a single argument (no spaces), -and the value substituted is the full path to the executable (no arguments -may be added). +system. The name of the command must be a single argument (no spaces in the +shebang executable), and the value substituted is the full path to the +executable (additional arguments specified in the .INI will be quoted as part +of the filename). .. code-block:: ini [commands] - /bin/sh=C:\Program Files\Bash\bash.exe + /bin/xpython=C:\Program Files\XPython\python.exe Any commands not found in the .INI file are treated as **Windows** executable paths that are absolute or relative to the directory containing the script file.