upgrade won't install newer version

[johndoe46]

I fail to upgrade a package, even though there's a newer version at pypi:

MacBook-Pro-de-Mickael-Desfrenes:~ mickael$ pip search pybean | grep LATEST
LATEST: 0.0.2
MacBook-Pro-de-Mickael-Desfrenes:~ mickael$ pip freeze | grep pybean
pybean==0.0.1
MacBook-Pro-de-Mickael-Desfrenes:~ mickael$ sudo pip install --upgrade pybean
Downloading/unpacking pybean
Running setup.py egg_info for package pybean

Installing collected packages: pybean
Found existing installation: pybean 0.0.1
Uninstalling pybean:
Successfully uninstalled pybean
Running setup.py install for pybean

Successfully installed pybean
Cleaning up...
MacBook-Pro-de-Mickael-Desfrenes:~ mickael$ pip freeze | grep pybean
pybean==0.0.1

[johndoe46]

I assume there's some kind of cache somewhere since installing on a blank machine I do get version 0.0.2...

[johndoe46]

I removed /Users/mickael/build/pybean and then re-run the install...

[jezdez]

I wasn't able to reproduce this, here's my console log:

[~] $ mkvirtualenv pybean
New python executable in pybean/bin/python
Installing setuptools............done.
Installing pip...............done.
virtualenvwrapper.user_scripts creating /Users/jezdez/.virtualenvs/pybean/bin/predeactivate
virtualenvwrapper.user_scripts creating /Users/jezdez/.virtualenvs/pybean/bin/postdeactivate
virtualenvwrapper.user_scripts creating /Users/jezdez/.virtualenvs/pybean/bin/preactivate
virtualenvwrapper.user_scripts creating /Users/jezdez/.virtualenvs/pybean/bin/postactivate
virtualenvwrapper.user_scripts creating /Users/jezdez/.virtualenvs/pybean/bin/get_env_details
[~] env:pybean $ pip install pybean==0.0.1
Downloading/unpacking pybean==0.0.1
  Downloading pybean-0.0.1.tar.gz
  Running setup.py egg_info for package pybean

Installing collected packages: pybean
  Running setup.py install for pybean

Successfully installed pybean
Cleaning up...
[~] env:pybean $ pip freeze
pybean==0.0.1
wsgiref==0.1.2
[~] env:pybean $ pip install -U pybean
Downloading/unpacking pybean
  Downloading pybean-0.0.2.tar.gz
  Running setup.py egg_info for package pybean

Installing collected packages: pybean
  Found existing installation: pybean 0.0.1
    Uninstalling pybean:
      Successfully uninstalled pybean
  Running setup.py install for pybean

Successfully installed pybean
Cleaning up...
[~] env:pybean $ pip freeze
pybean==0.0.2
wsgiref==0.1.2
[~] env:pybean $

I can only guess, but make sure you don't have an installation of pybean that pip can't uninstall due to permission issues. Using sudo shouldn't also be required if you are in a virtualenv (if that's the case, I'm not sure after looking at your log). Also, please make sure you have the latest version of pip installed (1.0.2 as of writing this).

[johndoe46]

I do install some libs system-wide for day-to-day use of some software so virtualenvs is not an option in this case. PIP is the latest version:

MacBook-Pro-de-Mickael-Desfrenes:pybean mickael$ pip --version
pip 1.0.2 from /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pip-1.0.2-py2.7.egg (python 2.7)

This seems to be at least specific to macosx since I can't reproduce this either on a debian box.

[jezdez]

Hm, do you happen to be in a directory containing a pybean distribution or code repository? Also, what does running sudo pip freeze give you? The same or a different version of pybean?

[carljm]

There now appears to be a pybean==0.0.3 up on PyPI? And upgrading to it works fine for me.

Most likely reason I can think of for the originally reported issue is that pybean had a 0.0.2 release registered on PyPI, but no actual code uploaded for 0.0.2. Clearly this is no longer the case, but the addition of 0.0.3 indicates the maintainer has made some changes on PyPI since this was reported.

(This is why I don't like "pip search" using the PyPI XML-RPC API. Opened #395 for that issue.)

[johndoe46]

Hm, do you happen to be in a directory containing a pybean distribution or code repository?

Yes, should it matter ?

but no actual code uploaded for 0.0.2

There was code uploaded.

[carljm]

It's possible that if there is a pybean/ directory in CWD that pip will privilege that over PyPI when you do "pip install pybean". I thought we'd fixed that already, but it's my best remaining idea. If so, that should probably be fixed so pip only privileges the local directory if explicit trailing / is provided. If that is the cause, please update summary/description accordingly and reopen.

If not, please reopen when you're able to provide consistent reproduction instructions. Thanks for the report!

[ysimonson]

In case anyone else hits this issue googling around, I managed to fix this issue with another package by upgrading to pip 1.4. Previously on 1.3, it would report a success when upgrading a package, but not actually upgrade. After updating pip to 1.4, I got this error message:

pip can't proceed with requirement 'catnap' due to a pre-existing build directory.
 location: /private/tmp/pip-build-root/catnap
This is likely due to a previous installation that failed.
pip is being responsible and not assuming it can delete this.
Please delete it and try again.

So I'm guessing pip 1.3 was silently failing to upgrade due to the same reason.