-
Notifications
You must be signed in to change notification settings - Fork 3
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
Consider a less ad-hoc approach to CLI arguments #10
Comments
A different CLI option:
There's not really anything special with reloading one module. Though perhap's it's normal? Use one python module as an entrypoint into your app, and consider other modules dependencies? @tingstad's new feature of "also reload watched files if they are a module and have been changed since last time" is really something a bit different. It's an ergonomic solution if the user writes a main module and other modules. |
Though. Do we actually need to change the CLI? Real issues:
Hypothetical issues:
Perhaps trying to fix the real issues directly is better than redoing the whole CLI. Potential new stuff:
|
GNU CLI conventions: https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html |
Nice argparse guide: https://realpython.com/command-line-interfaces-python-argparse/ |
Right now, we hand roll CLI arguments. We allow something like:
But this isn't reflected in the helptext.
I know we have argparse -- but argparse can feel a bit heavy. I've used https://github.com/babashka/cli a bit recently, and I love how lightweight it is. Essentially, you specify the type of each option. The CLI lib can then return a map of all the options. Argparse might still be the way to go, not sure.
Current helptext output:
The text was updated successfully, but these errors were encountered: