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 barry.scott, mhammond, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-12-20.06:22:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450592576.89.0.988931619283.issue25148@psf.upfronthosting.co.za>
In-reply-to
Content
> and the launcher was actually updated to match the registry key
> directly, rather than special-casing the "-32" suffix

It appears this has broken the launcher. A freshly-built py.exe from Python 3.5 doesn't seem to find older 32bit versions, while py.exe from older versions doesn't find the 32bit 3.5. Doesn't this break the entire reason for having the launcher in the first place?
History
Date User Action Args
2015-12-20 06:22:56mhammondsetrecipients: + mhammond, paul.moore, tim.golden, zach.ware, steve.dower, barry.scott
2015-12-20 06:22:56mhammondsetmessageid: <1450592576.89.0.988931619283.issue25148@psf.upfronthosting.co.za>
2015-12-20 06:22:56mhammondlinkissue25148 messages
2015-12-20 06:22:56mhammondcreate