New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python uninstaller leave registry entries #48028
Comments
Result: The uninstaller doesn't remove the registry folder |
Confirmed 2.6.5 installer leaves "HKLM\SOFTWARE\Python\PythonCore\2.6\Modules" on install/uninstall without \2.6\ key. I propose to mark it as 'low' priority. |
I imagine this affects 3.1 and 3.2 as well, but I haven't added them to versions since that hasn't been confirmed. |
Confirmed on 3.x. |
FWIW: contributions are welcome. |
Isn't there an issue around having multiple versions of Python installed? The top level folder should only be removed if the version of Python being uninstalled is the last installed Python. This means executing code on uninstall and doesn't seem worth the effort. If I'm correct in this then I would suggest closing as wontfix. |
The top level should be removed only when it is empty after Python that is being uninstalled removed its own branch. |
There should be a "function" to remove key if empty. BTW, what software is used to create (un)installer and where is Python code for it? |
See PC/_msi.c, Lib/msilib, and Tools/msi |
I think Installer has features to remove registry keys with no subkeys; we probably would need to declare that we create these keys, and then Installer might remove them automatically. |
I don't think this is worth the bother. I've checked my registry and the only entry under HKLM\SOFTWARE\Python is PythonCore, under this are the following. 2.6 Only 3.3 is live on my machine. Clearly the pythonwin keys aren't our responsibility. It's hardly a lot of data anyway so why worry about it? Yes I'm aware that it's good practice to clean up after yourself but in this case is it really worth the effort? |
What is the reason for not following the good practice? Is it so hard to fix? |
Nobody has contributed a patch in five years, so it apparently is pretty hard. |
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: