Open cschloer opened 3 years ago
Yes, I have it on my todo list :) I'm planning to work on that by the end of this year.
On Thu, Oct 22, 2020 at 10:10 AM Conrad Schloer notifications@github.com wrote:
At some point it would be great to migrate to frictionless-py ( https://github.com/frictionlessdata/frictionless-py). As it currently stands, I use dataflows as my main dependency. It would be nice to get the new API/updates from the frictionless-py library without having to have two of the code in my dependencies (for example the tabulator code).
Just creating this issue to get the conversation started. To my understanding frictionless py library isn't quite ready for this.
@roll https://github.com/roll @akariv https://github.com/akariv
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/datahq/dataflows/issues/147, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACAY5JRQKFL742TNMVDAVDSL7LGDANCNFSM4S2YZZYQ .
Awesome thanks!
Quick check in, while trying to evaluate some bits and pieces for GeoJSON support, any updates on this or plans how this might evolve?
@roll is the frictionless library ready for this migration?
Hi @cschloer, yes it's stable from frictionless@4.0
At some point it would be great to migrate to frictionless-py (https://github.com/frictionlessdata/frictionless-py). As it currently stands, I use dataflows as my main dependency. It would be nice to get the new API/updates from the frictionless-py library without having duplicate code in my dependencies (for example the tabulator code).
Just creating this issue to get the conversation started. To my understanding frictionless py library isn't quite ready for this.
@roll @akariv