-
Notifications
You must be signed in to change notification settings - Fork 9
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
Consider requiring psycopg2-binary instead of psycopg2 #12
Comments
Just pointing out that then other projects which use psycopg2, and also depend on sqlalchemy-postgres-copy, will now depend on both psycopg2 and psycopg2-binary, which could break things. |
@brianmaissy indeed. After reading a bit more here psycopg/psycopg2#674, it seems to be a common problem. |
It the moment I'm installing both and I haven't encountered any problem. But it is hardly the optimal solution.. |
I think if you install both one will overwrite the other. Which is fine as long as you don't care which one is installed, and both are of the same version. |
It might break when it tries to build psycopg2 though. |
@svisser that is the original issue. I was having problem building psycopg2 in docker because I do not have postgress installed in the image (nor do I want to) |
I had same problem. Re-installing psycopg2 using conda instead of using pip resolved the issue. |
psycopg2 version 2.8 no longer includes the binary wheels, and it is built on install. This can cause problems, like when using this package in a docker image
Thanks
The text was updated successfully, but these errors were encountered: