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.

Title: 3.4 cherry-pick: 7b3c40510a08 Windows uninstaller doesn't uninstall completly Python 3.4
Type: Stage:
Components: Versions: Python 3.4
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: larry Nosy List: larry, loewis, vstinner
Priority: release blocker Keywords:

Created on 2014-03-02 18:30 by loewis, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg212573 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2014-03-02 18:30
New changeset 7b3c40510a08 by Martin v. Löwis in branch 'default':
Issue #20748: Uninstalling pip does not leave behind the pyc of
msg212707 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-03-04 10:39
I don't understand the impact of #20748: what happens when 3.4rc2 is uninstalled? C:\Python34 is not removed because C:\Python34Lib\ensurepip\__pycache__\_uninstall.cpython-34.pyc still exist?

It is a regression of Python 3.4rc2, right?
msg212730 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2014-03-04 16:30
This is all correct. In rc1, uninstallation was clean (but installation failed when elevated privileges were necessary); in rc2, it always installs, but doesn't cleanly uninstall, leaving the installation directory with some subdirectories behind.
msg212818 - (view) Author: Larry Hastings (larry) * (Python committer) Date: 2014-03-06 17:25
Date User Action Args
2022-04-11 14:57:59adminsetgithub: 65030
2014-03-06 17:25:25larrysetstatus: open -> closed
resolution: fixed
messages: + msg212818
2014-03-04 16:30:13loewissetmessages: + msg212730
2014-03-04 10:40:12vstinnersettitle: 3.4 cherry-pick: 7b3c40510a08 -> 3.4 cherry-pick: 7b3c40510a08 Windows uninstaller doesn't uninstall completly Python 3.4
2014-03-04 10:39:51vstinnersetnosy: + vstinner
messages: + msg212707
2014-03-02 18:30:47loewiscreate