pip >= 8.0.0 fails because of egg-info files in python stdlib

Bug #1536638 reported by Florian Kisser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python2.7 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Up-to-date pip might fail because ubuntu ships some egg-info files for stdlib packages in /usr/lib/python2.7/, but egg-info files are only for locally installed packages.

How to reproduce with argparse:

$ virtualenv venv
$ . venv/bin/activate
$ pip install -U pip
$ pip install -U argparse
Collecting argparse
  Downloading argparse-1.4.0-py2.py3-none-any.whl
Installing collected packages: argparse
  Found existing installation: argparse 1.2.1
Detected a distutils installed project ('argparse') which we cannot uninstall. The metadata provided by distutils does not contain a list of files which have been installed, so pip does not know which files to uninstall.

Revision history for this message
Matthias Klose (doko) wrote :

no, egg-info files are not only for locally installed packages. almost every Python module in Ubuntu is shipped with an egg-info file.

Changed in python2.7 (Ubuntu):
status: New → Invalid
Revision history for this message
Florian Kisser (flok) wrote :

Yes, but not for python stdlib. This is Debian/Ubuntu specific (see debian/rules line 1040). Pip worked around this, but this strange patching might cause errors again in the future.

Revision history for this message
Barry Warsaw (barry) wrote :

OTOH, we're hoping pip will learn how to work better with distro provided packages.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.