➜

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 Jurko.Gospodnetić
Recipients Jurko.Gospodnetić
Date 2014-03-10.15:46:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394466404.86.0.786791371445.issue20883@psf.upfronthosting.co.za>
In-reply-to
Content 
A possible solution would be to update installers and runners to use HKEY_CURRENT_USER\Software\Wow6432Node registry entries for 32-bit 'for current user only' installations on a 64-bit Windows OS.

To preserve backward compatibility, runners could fall back to reading the 64-bit HKEY_CURRENT_USER\Software registry entries if their 32-bit counterparts can not be found directly.

This way:
  - installations on 32-bit Windows are unaffected
  - new installations work with new runners correctly
  - old installations work with new runners as before
  - old installations work with old runners as before
  - new 64-bit installations work with old runners as before
  - new 32-bit installations do not work with old runners
History
Date User Action Args
2014-03-10 15:46:44Jurko.Gospodnetićsetrecipients: + Jurko.Gospodnetić
2014-03-10 15:46:44Jurko.Gospodnetićsetmessageid: <1394466404.86.0.786791371445.issue20883@psf.upfronthosting.co.za>
2014-03-10 15:46:44Jurko.Gospodnetićlinkissue20883 messages
2014-03-10 15:46:44Jurko.Gospodnetićcreate