-
-
Notifications
You must be signed in to change notification settings - Fork 617
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
Error with packages where their setup.py egg_info
call fails
#343
Comments
Well, for more info, if one changes this line to
Which seems right as i don't have the build dependencies satisfied. But is ilogical that i have to met dependencies on an information command as egg_info. I will go on with my research and report here. |
Well, i've tracked this particular problem to this ticket psycopg/psycopg2#128, which is not a pip-tools problem. However, there are several other packages that have a bad written setup.py that causes an informative command as egg_info to fail if the build dependencies are not met or if the egg_info fails because of another unknown reason. Generally it seems to me that @nvie what do you think? |
More on this pypa/pip#661 |
Yeah, that would be ideal. This is notoriously hard with Python packaging though. As the thread you linked points out, Python packages don't carry static metadata, so they typically need to execute |
pip-compile
with psycopg2
setup.py egg_info
call fails
This just started happening to me, is there any workaround for it? This is my requirements.in:
|
Same here. When I comment out matplotlib it works.
|
still not working without matplotlib |
@asmaps This is an issue that is fixed in master (cannot make release, check #531) where @pablote could you provide your Note: If you decide to try with the code in master, be sure to run |
This is now fixed in 1.10.2 |
I recreated the virtualenv and now is working fine, thanks :) |
I was still seeing this issue with pip-tools 1.11.0 when trying to compile a bare-bones requirements.in containing only the word The issue was that the latest version of Django supports only Python 3.x, but my virtualenv was for Python 2.7. The solution was to pin Django in requirements.in: I don't know if pip-tools can do anything to clarify the cause of the error (it already shows the same error message that you'll see if you |
This is what I got when I have
psycopg2
in.in
file:The text was updated successfully, but these errors were encountered: