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 steve.dower, tim.golden, zach.ware
Date 2015-05-28.00:10:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
For 3.5 32-bit installs we register in a different key to avoid collisions with 64-bit installs, but now the 3.4 launcher can't find us.

If you have installed 3.4 for all users (likely) and then install 3.5 just-for-me (also likely), then you'll continue to get the 3.4 launcher, and there's no way to avoid this because there's no option to omit it.

I think we should backport the launcher to 3.4 so that the next 3.4 release will be able to also work with 3.5.

Date User Action Args
2015-05-28 00:10:57steve.dowersetrecipients: + steve.dower, tim.golden, zach.ware
2015-05-28 00:10:56steve.dowersetmessageid: <>
2015-05-28 00:10:56steve.dowerlinkissue24306 messages
2015-05-28 00:10:56steve.dowercreate