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 loewis
Recipients loewis
Date 2014-02-23.18:17:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1393179421.3.0.600062954886.issue20748@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2014-02-23 18:17:01loewissetrecipients: + loewis
2014-02-23 18:17:01loewissetmessageid: <1393179421.3.0.600062954886.issue20748@psf.upfronthosting.co.za>
2014-02-23 18:17:01loewislinkissue20748 messages
2014-02-23 18:17:00loewiscreate