➜

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 mhammond
Recipients mhammond, paul.moore, steve.dower, tim.golden, vinay.sajip, zach.ware
Date 2016-01-10.00:59:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452387575.38.0.184373942558.issue26070@psf.upfronthosting.co.za>
In-reply-to
Content 
The launcher was recently updated to look in PCBuild/win32 to support the win32 binaries being built in this directory instead of the top-level PCBuild directory. However, when this new launcher tries to find a binary for, say, Python 2.7, it doesn't find an executable because it's directly in PCBuild, not one of the win32 or amd64 sub-directories.

Note this only impacts Python when it is built in the directory - it doesn't impact installed versions.

The fix I came up with is to continue looking in PCBuild if it isn't found in one of those dirs.

Vinay, what do you think?
History
Date User Action Args
2016-01-10 00:59:36mhammondsetrecipients: + mhammond, paul.moore, vinay.sajip, tim.golden, zach.ware, steve.dower
2016-01-10 00:59:35mhammondsetmessageid: <1452387575.38.0.184373942558.issue26070@psf.upfronthosting.co.za>
2016-01-10 00:59:35mhammondlinkissue26070 messages
2016-01-10 00:59:34mhammondcreate