Eryk Sun added the comment:
In summary, the launcher documentation needs to be extended as follows:
* Include an example of a shebang with a normal Windows path:
#!"C:\Program Files\Python310\python.exe"
Highlight the importance of quoting paths that contain spaces.
New submission from Brendan Barnwell:
With the fix of issue #17903 in place, the behavior of the Windows launcher for
a shebang of #!/usr/bin/env python is now different from the behavior for the
other virtual commands in that the PATH is searched for this particular
virtual command but not
eryksun added the comment:
The patch for issue 23465 (PEP 486) updated the docs to explain the behavior of
#!/usr/bin/env as follows:
The /usr/bin/env form of shebang line has one further special
property. Before looking for installed Python interpreters,
this form will search the
