pip breaks after upgrading python package "requests"

[Nitzan Raz]

On Ubuntu 14.04, python-pip 1.5.4-1

After upgrading "requests" to 2.4, due to this commit:
https://github.com/kennethreitz/requests/commit/47d0517d66e8cf5832768262221f0357ae134ad1
"IncompleteRead" is removed from "requests.compat" and any pip invokation results in:

user@server:/tmp/pip/pip$ pip
Traceback (most recent call last):
  File "/usr/bin/pip", line 9, in <module>
    load_entry_point('pip==1.5.4', 'console_scripts', 'pip')()
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources.py", line 356, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources.py", line 2472, in load_entry_point
    return ep.load()
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources.py", line 2186, in load
    ['__name__'])
  File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 11, in <module>
    from pip.vcs import git, mercurial, subversion, bazaar # noqa
  File "/usr/lib/python2.7/dist-packages/pip/vcs/mercurial.py", line 9, in <module>
    from pip.download import path_to_url
  File "/usr/lib/python2.7/dist-packages/pip/download.py", line 25, in <module>
    from requests.compat import IncompleteRead
ImportError: cannot import name IncompleteRead

Woraround: Downgrade to requests=2.3.0 using easy_install:
sudo easy_install requests==2.3.0

Does not happen in Debian Wheezy (seems not to rely on "requests" at all in their version)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Simon Davy (bloodearnest)]

Looks like a fix is in progress upstream: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766419#23

[Barry Warsaw (barry)]

I think this is a different bug than the Debian one referenced in comment #2. It's actually

It's reproducible with:

$ pip install --upgrade --user requests
$ pip install --upgrade --user mistune

(any package after upgrading requests will trigger it)

I think the problem is that the wheels are only used inside a venv, but should probably be used everywhere. They are in /usr/share/python-wheels outside the venv though.

[Barry Warsaw (barry)]

Oops! "It's actually..." https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744145

[Launchpad Janitor (janitor)]

This bug was fixed in the package python-pip - 1.5.6-5ubuntu1

---------------
python-pip (1.5.6-5ubuntu1) vivid; urgency=medium

  * Merge with Debian. Remaining changes:
    - debian/patches/set_user_default.patch: Default to --user on non
      virtualenv.
  * Merge closes LP: #1363642

python-pip (1.5.6-5) unstable; urgency=medium

  * Team upload.
  * Use the .whl files for de-vendorized dependencies both inside and
    outside the virtual environments. (Closes: #744145)
  * d/control: Bump Standards-Version with no other changes necessary.
  * d/patches/use-venv-wheels.patch: Renamed to use-wheels.patch
 -- Barry Warsaw <email address hidden> Sun, 01 Mar 2015 10:33:01 -0500