Open manics opened 2 years ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
I'm :+1: for a switch to argparse!
One factor when choosing between argparse and traitlets is how we want to handle extensions and their configuration.
Proposed change
Switch from
tornado.options
toargparse
(or traitlets, though argparse is easier for a small utility like this) for handling command line argumentsAlternative options
Do nothing
Who would use this feature?
Anyone wanting a nice help message. Currently it looks like this
Problems include:
/opt/conda/envs/test/lib/python3.9/site-packages/jupyterhub_idle_culler/__init__.py
--cull-users
instead of--cull-users=true
), what values can they take (is it justtrue
/false
, or are other values like0
/1
accepted)=
is required (--url http://localhost/
is invalid)/opt/conda/envs/test/lib/python3.9/site-packages/tornado/log.py options
are arguably irrelevant(Optional): Suggest a solution
Use argparse instead. Boolean options would be implemented as
choices=["true","false"]
instead of a flag for compatibility.Get rid of the logging options? This would be a breaking change though.