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 chrullrich
Recipients chrullrich, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-09-18.08:06:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442563581.64.0.527655601006.issue25162@psf.upfronthosting.co.za>
In-reply-to
Content
The new Windows installer always places the uninstallation registry key into HKCU of the executing user. This is correct for a per-user installation, but when run with InstallAllUsers=1, the key should go into HKLM instead.

The "Programs and Features" list of installed applications is assembled from the HKLM and HKCU keys. In many cases, a system-wide installation will be performed by temporarily elevating the installer to a user account with administrator privileges on the local system. However, since Vista, the "Programs and Features" list is always run in the logged-on user's Explorer process, even when started by a different user (such as in an elevated command prompt). With the uninstallation key going into HKCU of some administrative account, the Python installation will not appear in this list, hence, cannot easily be removed.

Ceterum censeo: This bug would have been avoided by using MSI as the distribution package format.
History
Date User Action Args
2015-09-18 08:06:21chrullrichsetrecipients: + chrullrich, paul.moore, tim.golden, zach.ware, steve.dower
2015-09-18 08:06:21chrullrichsetmessageid: <1442563581.64.0.527655601006.issue25162@psf.upfronthosting.co.za>
2015-09-18 08:06:21chrullrichlinkissue25162 messages
2015-09-18 08:06:21chrullrichcreate