[issue34274] Python launcher behavior with "#!/usr/bin/env python" shebang

Change by Steve Dower : -- superseder: -> py.exe ignored PATH when using python3 shebang ___ Python tracker ___ ___ Python-bugs-lis

[issue34274] Python launcher behavior with "#!/usr/bin/env python" shebang

Steve Dower added the comment: This is not strictly a duplicate of issue28686, but it's close enough, so let's keep the discussion of changing the original shebang behaviour over on that issue. -- resolution: -> duplicate stage: -> resolved status: open -> closed _

[issue34274] Python launcher behavior with "#!/usr/bin/env python" shebang

Eryk Sun added the comment: See the discussion in issue 28686 regarding the use of version detection and/or versioned executable names with env shebangs. I think the launcher should at least support searching PATH for pythonX.exe and pythonX.Y.exe, so users can at least manually copy or syml

[issue34274] Python launcher behavior with "#!/usr/bin/env python" shebang

New submission from Segev Finer : When using the common "#!/usr/bin/env python" shebang, recent versions of the Python launcher will search the PATH for "python" as specified in the shebang. But Python on Windows installs as python.exe for all versions, both 2 and 3. So in a PC where Python 3

[issue34274] Python launcher behavior with /usr/bin/env python shebang

Change by Segev Finer : -- components: Windows nosy: Segev Finer, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Python launcher behavior with /usr/bin/env python shebang type: behavior versions: Python 3.7 _