This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Segev Finer
Recipients Segev Finer, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-07-29.21:47:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532900839.39.0.56676864532.issue34274@psf.upfronthosting.co.za>
In-reply-to
Content
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 is first on PATH, this shebang will choose Python 3. That's in contrast to any other shebang like "#!python" or "#!/usr/bin/python" which will prefer Python 2.

That's rather subtle and confusing...

To the best of my knowledge most Linux distros still install Python 2 as python and Python 3 as python3 (I think that's in the Makefile too). But of course there might also be distros that install python3 as python.
History
Date User Action Args
2018-07-29 21:47:19Segev Finersetrecipients: + Segev Finer, paul.moore, tim.golden, zach.ware, steve.dower
2018-07-29 21:47:19Segev Finersetmessageid: <1532900839.39.0.56676864532.issue34274@psf.upfronthosting.co.za>
2018-07-29 21:47:19Segev Finerlinkissue34274 messages
2018-07-29 21:47:19Segev Finercreate