-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setuptools: ModuleNotFoundError: No module named 'six' #964
Comments
That's right. This change was made intentionally as part of the Setuptools 34 release - dropping support for self install and upgrade. We've removed the hack that vendors setuptools dependencies. You'll want to install the dependencies with pip first. See bootstrap.py for one technique for installing the dependencies. |
I'm sorry if I'm slow to understand, but I have more questions. I don't see What is the recommended packaging procedure if you only have python installed to get to packages for pip and setuptools? And to make it absolutely clear, I'm not asking for end-user instructions, but for packaging instructions, i.e. a way to come up with binary packages for users when building from scratch without using prepackaged binaries. |
For anyone else stumbling over this issue, my solution was:
|
I got the same problem after I upgrade python2.7.10 to python2.7.13. None of the above works for me. |
See pypa/setuptools#964 for a few more details. Currently quite a few travis and circleci jobs are failing because of that.
* Install six before we upgrade setuptools. See pypa/setuptools#964 for a few more details. Currently quite a few travis and circleci jobs are failing because of that. * Explicitly upgrade pip and setuptools in 'make update_deps' so for travis too. * Potentially fix circleci * Fix setuptools and potentially docs environments * More explicitly install six and setuptools * Add more requirements for docs * Add pyparsing dependency
I wish that dependency would be lifted when Python 3 is being used. |
That dependency will be lifted when Python 2.7 support is dropped. Until then, |
Building setuptools in the standard way I've used forever fails:
It looks like setuptools now added a six dependency, which breaks distributions that build from scratch, because six uses setuptools for installation (dependency cycle).
The text was updated successfully, but these errors were encountered: