This bug matters. I have a pretty vanilla installation, python, matplotlib, and a few other standard packages, all from the official repositories. After a recent apt-get update, I now get the same exact pip breaking result as the first comment.
The workaround was to use easy_install to install pip, then use pip2.7 to install what I wanted. But I presume that is not the intended path for typical users.
This bug matters. I have a pretty vanilla installation, python, matplotlib, and a few other standard packages, all from the official repositories. After a recent apt-get update, I now get the same exact pip breaking result as the first comment.
The workaround was to use easy_install to install pip, then use pip2.7 to install what I wanted. But I presume that is not the intended path for typical users.