You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What's the rationale for having the CLI be separate? It seems like it would be easy enough to ship along with the main Python library?
I think it comes from my aversion to click being pulled in to Python libs when you don't want it — in the same manner, if we don't need clap in our Python package let's not include it. However, the downside is that we take up two packages instead of one, and folks might be surprised when the pip install cql2doesn't come with a CLI.
Really happy w/ either, I don't have a strong preference.
I assume that clap is relatively small. I doubt it increases the bundle size of the wheels much at all. I figure unless you have big dependencies that you need to keep separate, the simplicity of having a single wheel building process is preferred.
Over at stac-rs I used a separate Python package (https://pypi.org/project/stacrs/ and https://pypi.org/project/stacrs-cli/) and I think we should do the same here, since the CLI is a separate crate. So that'd be
cql2-cli
on PyPI.The text was updated successfully, but these errors were encountered: