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
zest.releaser need setuptools/distribute installed at system level when used in buildout #24
Comments
zest.releaser requires setuptools in its setup.py. My assumption is that you have setuptools installed globally (else, how did you install zest.releaser?) OR that you installed it into some virtualenv or buildout. In both cases, I'd expect setuptools to be available when using sys.executable. But apparently I'm mistaken! It could very well be that it works just fine with virtualenv (which seems to be having a harder link to its own custom local python than buildout). Do you have any idea how we could solve this? |
The #!/usr/bin/python2.7
import sys
sys.path[0:0] = [
'/home/xxxxx/.buildout/eggs/zest.releaser-3.37-py2.7.egg',
'/home/xxxxx/.buildout/eggs/distribute-0.6.28-py2.7.egg',
]
import zest.releaser.fullrelease
if __name__ == '__main__':
zest.releaser.fullrelease.main() So with I agree with you that a pythonist machine without setuptools installed is quite rare :) I've not tried it but a solution could be to update |
I'm also bitten by this
updating PYTHONPATH and appending the path to zestreleaser's setuptools-path seems OK |
A few years ago I gave this a shot in the maurits-add-syspath branch, basically changing the Let's try it again, in basically the same way. See branch maurits-issue-24. |
BTW, a workaround for the user would be to create a virtualenv or buildout or whatever with a setuptools installed and add the directory containing that python executable to the path when calling fullrelease or release:
If you make this a small bash script or an alias and give that the name |
I just released 3.51 with the fix by @mauritsvanrees . @woutervh, could you try that one? (If it is still a problem, re-open the ticket :-) ) |
Confirmed that the fix is working. |
When running
fullrelease
into a buildout, I got a traceback as version.After investigating,
setup.py --version
is called withsys.executable
in apopen
thus lost thesys.path
context.Most method are in
zest/releaser/utils.py
file.The problem append when the computer have no version of setuptools installed at system level.
The text was updated successfully, but these errors were encountered: