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 peter@psantoro.net, steve.dower, tim.golden, zach.ware
Date 2014-12-27.15:46:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1419695195.38.0.841011815786.issue23120@psf.upfronthosting.co.za>
In-reply-to
Content
I'm already quite keen to rename the registry key for 32-bit on Windows, since there are some places where that will cause conflicts. This won't be done for 3.4 though, as we don't have an active maintainer for the old installer (Martin is still building them, but not working on it). I haven't yet thought about how the updated keys should look, but when I get time to get back to the installer I'll try some things.

The 3.5 installer shouldn't have this issue as it will use product codes to detect other Python installations rather than registry keys.
History
Date User Action Args
2014-12-27 15:46:35steve.dowersetrecipients: + steve.dower, tim.golden, zach.ware, peter@psantoro.net
2014-12-27 15:46:35steve.dowersetmessageid: <1419695195.38.0.841011815786.issue23120@psf.upfronthosting.co.za>
2014-12-27 15:46:35steve.dowerlinkissue23120 messages
2014-12-27 15:46:34steve.dowercreate