Bundling as package? #21
Comments
|
Hi @SimonGoring! To be honest, it's mostly we just haven't gotten around to it :). Tonic has a commercial subsetter that is a part of the product itself, which comes with a host of other features and performance improvements, and often gets a bit more of our time. If that's something that would interest you, do feel free to let us know. However, we'd certainly welcome a contribution to support this! I've been wanting to add go down the route of having Poetry manage packaging and dependencies in a pyproject.toml file in particular, but we'd be open to other possibilities. |
|
Hi, thanks, and sorry for the delay in replying. Totally understood about the focus. I opened another issue, this is certainly something I'm interested in supporting, or helping with, and I'll poke around. Just need to figure out some of the mechanics :) |
Hi, this is probably more of a feature request, but I've just found this project and it is exactly what I needed to help with the Neotoma Paleoecology Database, to export subsets of the data to our partners on a periodic basis.
Because we are a distributed organization, and because our
initial_targets['where']statement varies by partner I had started thinking about ways to modify theconfig.jsonprogrammatically, and to bundle this as a (forked) script that would live in our GitHub repos.From a design perspective I was wondering if there was a specific reason this wasn't written as a more formal Python package. Is this a potential contribution you would welcome?
The text was updated successfully, but these errors were encountered: