Skip to content

Commit a3510c3

Browse files
gh-100247: Improve documentation for custom shebang commands in py.exe launcher (GH-101083)
(cherry picked from commit 30753c3) Co-authored-by: Steve Dower <steve.dower@python.org>
1 parent 87ade7e commit a3510c3

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

Doc/using/windows.rst

+5-4
Original file line numberDiff line numberDiff line change
@@ -867,14 +867,15 @@ The environment variable :envvar:`PYLAUNCHER_NO_SEARCH_PATH` may be set
867867
Shebang lines that do not match any of these patterns are looked up in the
868868
``[commands]`` section of the launcher's :ref:`.INI file <launcher-ini>`.
869869
This may be used to handle certain commands in a way that makes sense for your
870-
system. The name of the command must be a single argument (no spaces),
871-
and the value substituted is the full path to the executable (no arguments
872-
may be added).
870+
system. The name of the command must be a single argument (no spaces in the
871+
shebang executable), and the value substituted is the full path to the
872+
executable (additional arguments specified in the .INI will be quoted as part
873+
of the filename).
873874

874875
.. code-block:: ini
875876
876877
[commands]
877-
/bin/sh=C:\Program Files\Bash\bash.exe
878+
/bin/xpython=C:\Program Files\XPython\python.exe
878879
879880
Any commands not found in the .INI file are treated as **Windows** executable
880881
paths that are absolute or relative to the directory containing the script file.

0 commit comments

Comments
 (0)