[issue20748] 3.4rc2 MSI uninstallation leaves behind ensurepip _uninstall .pyc

Martin v. Löwis report at bugs.python.org
Sun Feb 23 19:17:01 CET 2014


New submission from Martin v. Löwis:

The installer currently leaves behind a single pyc file, namely 

Lib\ensurepip\__pycache__\_uninstall.cpython-34.pyc

I believe that the problem is that installer computes the list of files to be removed in the script generation phase, finding out what files match __pycache__\*.*. The _uninstall .pyc is not there yet. Then, during script execution, first pip uninstallation is run, creating the pyc file, then the (precomputed) list of files is removed.

In rc1, this was not a problem because PIP removal happened in the UI phase (i.e. before script execution); this was changed to support elevated privileges in #20641.

The simplest work-around could be to run pip uninstallation with -B. I just edited the MSI with orca, and that seems to work fine.

If anybody can suggest how installer could be instructed to remove the .pyc regularly through the RemoveFiles action, I'd appreciate any help.

----------
messages: 212014
nosy: loewis
priority: release blocker
severity: normal
status: open
title: 3.4rc2 MSI uninstallation leaves behind ensurepip _uninstall .pyc

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20748>
_______________________________________


More information about the Python-bugs-list mailing list