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 eryksun
Recipients eryksun, paul.moore, ricpol, steve.dower, tim.golden, wdhwg001, zach.ware
Date 2017-02-08.23:44:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486597473.16.0.340469305487.issue28686@psf.upfronthosting.co.za>
In-reply-to
Content
If the system doesn't have a "python3.exe" on PATH, then "env python3" will run a registered version, exactly like it currently does. IMO, this is slightly less confusing than the current behavior, which skips searching PATH in this case. We can take it a step further, however. If the launcher can't find the versioned name, then search for "python[w].exe" and determine its version using the approach I outlined above. If it doesn't match the required version, as always the launcher will default to running a registered version.
History
Date User Action Args
2017-02-08 23:44:33eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, wdhwg001, ricpol
2017-02-08 23:44:33eryksunsetmessageid: <1486597473.16.0.340469305487.issue28686@psf.upfronthosting.co.za>
2017-02-08 23:44:33eryksunlinkissue28686 messages
2017-02-08 23:44:33eryksuncreate