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

csvkit 0.9.1 dependency - update to current version (1.0.2) #597

Closed
haylo75 opened this issue Nov 16, 2017 · 4 comments
Closed

csvkit 0.9.1 dependency - update to current version (1.0.2) #597

haylo75 opened this issue Nov 16, 2017 · 4 comments

Comments

@haylo75
Copy link

haylo75 commented Nov 16, 2017

I just started using dbt and really like it so far. We have a good handle on EL in our data pipeline to Redshift, with a need to tool out & template the T. With that said, I manage a large suite of pip packages for our pipeline. I tried adding dbt to my pip-compile package list but have come across a dependency conflict.

I noticed in setup.py there is a version-pegged dependency on csvkit==0.9.1. From what I can see, this package is referenced solely in seeder.py, importing table and sql. csvkit 0.9.1 was released on 2015-03-30. The current version is 1.0.2, released on 2017-04-28. Would it be possible to update this dependency?

@drewbanin
Copy link
Contributor

Hey @haylo75 -- dbt uses csvkit as a library which, last I checked, it not really not how it's supposed to be used anymore.

dbt imports table and sql from csvkit, but these modules don't exist in newer releases of csvkit anymore!

Our plan is to drop the csvkit dependency entirely and instead use agate directly for CSV-related things.

I just created a proper issue for this here: #598. We intend to tackle this in the relatively short term.

Thanks for writing -- lmk if there's anything else I can help with!

@haylo75
Copy link
Author

haylo75 commented Nov 16, 2017

Thanks a lot for the quick response @drewbanin - I thought based on the CSV tagged tickets I read you might be moving away from csvkit. agate is definitely a good move IMO. I'll keep an eye on #598, thanks!

@haylo75 haylo75 closed this as completed Nov 16, 2017
@drewbanin
Copy link
Contributor

no prob @haylo75! Not sure if you've seen, but we have a pretty active slack community -- feel free to pop in there if you have any other quick questions.

@haylo75
Copy link
Author

haylo75 commented Nov 16, 2017

Thanks, I didn't know about the slack community!

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