Consider requiring psycopg2-binary instead of psycopg2

[CaselIT]

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

[brianmaissy]

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.

[CaselIT]

@brianmaissy indeed.

After reading a bit more here psycopg/psycopg2#674, it seems to be a common problem.
I guess the best solution would be to remove the dependency altogether and add a clearer error than the default ImportError if an user tries to use this library without psycopg2

[CaselIT]

which could break things.

It the moment I'm installing both and I haven't encountered any problem. But it is hardly the optimal solution..

[brianmaissy]

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.

[svisser]

It might break when it tries to build psycopg2 though.

[CaselIT]

@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)

[rsemihkoca]

I had same problem. Re-installing psycopg2 using conda instead of using pip resolved the issue.