Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

"pip install -U" doesn't upgrade #634

Closed
ronaldoussoren opened this Issue Aug 13, 2012 · 3 comments

Comments

Projects
None yet
3 participants

On at least one of my machines "pip install -U" doesn't always upgrade packages.

This might be because there happened to be a subdirectory named "build" in the current working directory that contained a extracted source archive of an older version.

Command-line output:

$ $ pip install -U pytz lxml
Downloading/unpacking pytz from http://pypi.python.org/packages/source/p/pytz/pytz-2012d.tar.gz#md5=bf01c4fc9b64b164c3e2bb9c5477a544
Running setup.py egg_info for package pytz

warning: no files found matching '*.pot' under directory 'pytz'
warning: no previously-included files found matching 'test_zdump.py'

Downloading/unpacking lxml from http://pypi.python.org/packages/source/l/lxml/lxml-2.3.5.tar.gz#md5=730bb63383528b65eaa099d64ce276cf
Running setup.py egg_info for package lxml
Building lxml version 2.3.4.
Building without Cython.
Using build configuration of libxslt 1.1.26
Building against libxml2/libxslt in the following directory: /usr/lib64

Installing collected packages: pytz, lxml
Found existing installation: pytz 2012c
Uninstalling pytz:
Successfully uninstalled pytz
Running setup.py install for pytz

warning: no files found matching '*.pot' under directory 'pytz'
warning: no previously-included files found matching 'test_zdump.py'

Found existing installation: lxml 2.3.4
Uninstalling lxml:
Successfully uninstalled lxml
Running setup.py install for lxml
Building lxml version 2.3.4.
Building without Cython.
Using build configuration of libxslt 1.1.26
Building against libxml2/libxslt in the following directory: /usr/lib64

Not how pip downloaded lxml 2.3.5 and then says it is building 2.3.4.

After this I noticed a directory named "build" in the current working directory. After removing this directory I could perform the upgrade.

IMHO this is a bug because pip shouldn't take notice of the contents of the CWD.

Contributor

carljm commented Aug 14, 2012

Yes, this is a known bug, and should be fixed. It may already have an issue, but I'm not finding it at the moment, so leaving this open to track it.

Contributor

qwcode commented Oct 29, 2012

related issue #709

Contributor

qwcode commented Apr 20, 2013

closing due to merge of #865

@qwcode qwcode closed this Apr 20, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment