No Module Named Setuptools
Hi Arnaud, I think this is because paver internally uses setuptools (also known as easy-install) so you need that installed, otherwise it doesn't work. UPDATE: Distribute seems to be obsolete, i.e. Merged into Setuptools: Distribute is a deprecated fork of the Setuptools project. Since the Setuptools 0.7 release, Setuptools and Distribute have merged and Distribute is no longer being maintained. All ongoing effort should reference the Setuptools project and the Setuptools documentation.
Help on package pip.vendor.requests in pip.vendor:NAMEpip.vendor.requestsPACKAGE CONTENTSversioninternalutilshelppackagesFILE(built-in)(END). No wonder pip couldn't import requests.exceptions.
And since it's a vendored package, reinstalling python-requests doesn't do anything. I can't reproduce the problem with a clean virtualenv, so I suspect my pip.vendor.requests might just be broken. But I really don't know, so are there any ideas on how I could fix this?Last edited by imyxh (2018-05-27 18:51:16). Well, this is the pip from testing, yes.But I don't get this error message at all, and I'm extremely confused where it comes from, since the pip in testing correctly depends on requests (hence why it works for me).The bugreport you linked, jasonwryan, discusses how we switched this, which presumably does have something to do with the issue, but unfortunately not in a way which provides obvious clues what the issue is.It also links to which details the completely different issue of incompatible pip.vendor.packaging vs pip.vendor.pkgresources.extern.packaging which is slightly different.
So pip is definitely broken, just not like this???(We discussed this a bit on IRC.). The pip in testing correctly depends on requests (hence why it works for me)Well, my version of python-pip also depends on requests. I probably goofed something up on the install.I suppose this thread is solved, for now at least.I had the exact same issue as the original post on one Arch machine but not another with the pip 10.0.1 upgrade. I don't ever recall miss-using pip on either machine. Either way your above quoted work-around solved my issue as well (for now). Pip now runs, but I've yet to try to install or upgrade any packages with it yet.
No Module Named Setuptools Centos
I hope it works!Useless side note: Upgrading your package manager shouldn't cause nebulous errors. If anyone can explain why this happened, that would be awesome. I'm fully aware that I'm not offering any useful clues because frankly I don't even know where to start. It's been thoroughly confirmed that a number of people who all had pip break the exact same way, all had untracked files (not part of the pip package) installed in pip's module directory.This is bad, because it means.someone. (maybe you did but forgot, maybe you did it in your sleep, maybe your roommate/neighbor did it to be 'funny', assuming they even know how to use Arch Linux) ran 'sudo pip install -upgrade pip' in order to get a newer version of pip than the one pacman knew about. The result is that pip broke, because you had the conflicting bits and pieces of two installs floating around in the same folder trying to use each others' incompatible files.Lesson learned: do not use sudo pip, ever. Use 'pip install -user' or proper virtualenv setups.You can even force -user to be default.