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

Command-line Parsing #3

Open
Mierdin opened this issue Nov 28, 2016 · 4 comments
Open

Command-line Parsing #3

Mierdin opened this issue Nov 28, 2016 · 4 comments
Milestone

Comments

@Mierdin
Copy link
Contributor

Mierdin commented Nov 28, 2016

We need to implement a module that parses command-line arguments and parameters. The base command can be something like bdot, and then after that we can put in some subcommands like bdot earth, and that will output some data about the Earth API.

We might also want some optional parameters

@gamefiend
Copy link
Contributor

Do we want to use something like Click. Jeorry suggested this in the Slack channel, but I had been thinking about it too and wanted to second it.

It seems like a reasonable framework for setting up commands and subcommands.

@Mierdin
Copy link
Contributor Author

Mierdin commented Dec 1, 2016

Personally I would recommend we go with the canonical Python approach whenever possible (i.e. stdlib) so we can include as many folks as possible. In this case it would be argparse, which is actually not that bad to work with.

@jeorryb
Copy link

jeorryb commented Dec 2, 2016

I'm good with argeparse. I was going to tackle the patent API first as a warmup.

@gamefiend
Copy link
Contributor

I am good with argparse too! I will actually get working on setting up the cli structure (more on that in another issue).

@Mierdin Mierdin added this to the First Release milestone Dec 2, 2016
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

3 participants