You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/zooba'closed_at=<Date2015-10-01.22:21:01.841>created_at=<Date2015-09-18.09:03:04.029>labels= ['type-bug', 'expert-installation', 'OS-windows']
title='Windows uninstallation should not remove launcher if other versions remain'updated_at=<Date2015-10-01.22:21:01.840>user='https://github.com/chrullrich'
Uninstalling 3.5 on Windows removes the py.exe launcher. If it was installed in the system-wide path (%SYSTEMROOT%), it may have replaced an existing copy from an earlier version. In this case, removing the launcher will break this remaining installation, requiring a repair.
Instead, the launcher should not be deleted. It uses the static CRT, hence has no DLL dependencies that would be removed by the uninstallation, and it will -- as PEP-397 demands -- select the Python version it starts based on the command line and the available installations.
Ceterum censeo: This bug could have been avoided by using MSI as the distribution package format and using the same component code for the launcher file in all supporting versions. Even if the file itself is different, the identical component code would have ensured through reference counting that it would only have been removed with the last referencing installation. Upward compatibility of older launchers could have become a problem, though.
I'm going to look into having the launcher's MSI stay behind when the bundle is removed, so it will have to be uninstalled separately. It can already be installed separately, though there isn't a really easy way to get the installer so you can do that.
(Because prior versions of Python did not always use the same component ID for the launcher, we have to have a break here. However, we now have a single MSI that is identical for all future versions, so the problem should not arise again.)
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: