[issue19141] Windows Launcher fails to respect PATH

Vinay Sajip added the comment: Closing, as no activity following Mark's comment. -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___

[issue19141] Windows Launcher fails to respect PATH

Mark Hammond added the comment: > I am trying to draw attention to the situation where the script has no > shebang line, and there is no other explicit configuration info for > py.exe. In that case, the user should just type "python scriptname.py" - py.exe is for cases where just specifying "py

[issue19141] Windows Launcher fails to respect PATH

Graham Wideman added the comment: Hi Vinay, thanks for commenting. And of course for your efforts on py.exe (and no doubt the debate process.) I am trying to draw attention to the situation where the script has no shebang line, and there is no other explicit configuration info for py.exe. (N

[issue19141] Windows Launcher fails to respect PATH

Vinay Sajip added the comment: The current version of py.exe *does* do a PATH search for a shebang of "#!/usr/bin/env python" (see #17903). The whole *point* of py.exe is to invoke Pythons which are *not* available on the PATH. The behaviour of py.exe is as documented in PEP 397, other than t

[issue19141] Windows Launcher fails to respect PATH

Changes by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue19141] Windows Launcher fails to respect PATH

New submission from Graham Wideman: Python Launcher for Windows provides some important value for Windows users, but its ability to invoke python versions not on the PATH is a problem. py.exe chooses a version of Python to invoke, in more or less this order of decreasing priority; it is the *l