-
Notifications
You must be signed in to change notification settings - Fork 2
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
Some tools still use getopts #48
Comments
pfuntner
added a commit
that referenced
this issue
Oct 17, 2020
These changes specifically address: - #21: I added use of argparse & logging (#48 also mentions fitwidth but it is more global and #22 is specific about fitwidth) - #39: By makind use of argparse, this problem goes away! No more lame command line parsing! - #66: I had brushed this one off but I went ahead but there was a simple fix so I was able to address it easily.
I went ahead and fixed this issue in
I don't even think I use all of these... |
I gave |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A lot of tools still use the
getopts
module so there are some inconsistencies regarding how options work between tools, some lack some features like the--help
option or--foo bar
and--foo=bar
being synonymous, etc. A lot of tools are already usingargparse
but not all.I used
grep -lr getopt
to get a list of the tools that use getopt and will sort them with the most desirable tools toward the top:Some of these I probably don't even use much anymore or have been replaced by other tools so I don't know if I'll ever hit them all. But I could get to a point where I consider the issue closed.
As I fix these, I'll remove them from the list.
This was also reported by #21 forfitwidth
The text was updated successfully, but these errors were encountered: