Skip to content
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

tap-postgres incompatible with singer-target-postgres #99

Open
brian-bk opened this issue Jul 28, 2020 · 1 comment
Open

tap-postgres incompatible with singer-target-postgres #99

brian-bk opened this issue Jul 28, 2020 · 1 comment

Comments

@brian-bk
Copy link

This is a pretty annoying aspect between packages maintained between singer-io and datamill-co orgs. This project seems to be the more out-of-date one.

Compare this project (tap-postgres):

'psycopg2==2.7.4',

to the datamill maintained project (singer-target-postgres):
setup.py link which contains

        'psycopg2==2.8.5',

This makes it impossible to install both tap-postgres and singer-target-postgres in the same python environment.

Another side-issue is in the singer docs page for the target, it recommends installing target-postgresql, which does not exist on pypi. There's a package target-postgres maintained by statsbot but the docs link to datamill's maintained project singer-target-postgres. It's a bit risky to not reference a clear package.

@astrojuanlu
Copy link

From the Singer FAQ:

https://github.com/singer-io/getting-started/blob/master/docs/FAQ.md#how-do-i-prevent-dependency-conflicts-between-my-tap-and-target

To prevent conflicts, we recommend running taps and targets in separate virtual environments. That helps isolate the dependencies for each. See instructions for doing this here.

I believe taps and targets are not meant to be installed in the same environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants