-
Notifications
You must be signed in to change notification settings - Fork 170
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
Run easy_install with specified setuptools_version #222
Conversation
If setuptools is installed globally by easy_install then the easy_install.pth gets added to sys.path before PYTHONPATH and the wrong setuptools version is used.
Would it be possible to add a test ? |
Unfortunately I can't see a way to test this. |
Virtually the same change as in #232 for the actual buildout code. So this one is best merged, too. Once a new release is out, the new bootstrap needs to be placed in some of the regular places. Who normally does this? |
Run easy_install with specified setuptools_version, same change as #232
@reinout I think @jimfulton is the one who can manage download.buildout.org |
@tseaver @reinout The bootstrap.py is at https://bootstrap.pypa.io/bootstrap-buildout.py |
The last modification date, if you look at the dir listing at https://bootstrap.pypa.io/ is 14-Dec-2014. So it doesn't look too automatic to me :-) There is also a Would it be a good idea to add information about updating the bootstrap to |
#86 has more info on how the boostrap.py actually ends up in the various places. I'm writing it down in |
This one needs a release (#249), too, because of the inherent bootstrap.py release. |
If setuptools is installed globally by easy_install then the easy_install.pth gets added to sys.path before PYTHONPATH and the wrong setuptools version is used.