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 steve.dower
Recipients eryksun, paul.moore, ricpol, steve.dower, tim.golden, wdhwg001, zach.ware
Date 2017-02-06.22:41:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486420917.23.0.756328202655.issue28686@psf.upfronthosting.co.za>
In-reply-to
Content
> If Python on Windows changed to ship python3.exe and python37.exe alongside python.exe, then it might be worth revisiting this discussion

Agreed, though if we started including versioned executables wouldn't that resolve this issue naturally? (As in, we'd search for python3.exe and find it?)

FWIW, I'm not a huge fan of including versioned executables - I would much rather include versioned *launchers*, so we can put them all in the one directory and avoid cluttering the search path (i.e. rename "py.exe" to "python.exe", "python2.exe" and "python3.exe" and have it check its own name before searching).
History
Date User Action Args
2017-02-06 22:41:57steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, eryksun, wdhwg001, ricpol
2017-02-06 22:41:57steve.dowersetmessageid: <1486420917.23.0.756328202655.issue28686@psf.upfronthosting.co.za>
2017-02-06 22:41:57steve.dowerlinkissue28686 messages
2017-02-06 22:41:57steve.dowercreate