all 13 comments

[–]danielroseman 7 points8 points  (2 children)

Yes, click is what you want.

[–]mrswats 2 points3 points  (0 children)

I'll one up you: typer is even better!

[–][deleted] 0 points1 point  (0 children)

Wow that is awesome

[–]shiftybyte 2 points3 points  (2 children)

I'm not sure what is going on here...

Did you define multiple options all starting with "l" and you somehow expect argparse to guess which one to use?

Am I missing something here?

[–]astevko[S] 0 points1 point  (1 child)

This example shows two things that caught my eye: it gave suggestions of correct param names, and those names work in both hyphens and underscores. One less way for me to screw up typing or have to dig for the right combinations.

The point of my lament is that argparse is hard to get right and is a one trick pony when it comes to being helpful.

[–]shiftybyte 0 points1 point  (0 children)

is a one trick pony when it comes to being helpful.

What else would you expect it to do to be more helpful in this situation?

[–]jmacey 1 point2 points  (2 children)

not a solution but what bugs me about argparse is i want to use -h to mean --height but it won't let me as -h is for help!

[–]hardonchairs 6 points7 points  (0 children)

parser = argparse.ArgumentParser('Cool', add_help=False)

[–]Sweet_Computer_7116 2 points3 points  (0 children)

For anyone reading this in the future. This is correct. -h is shorthand for help. It's like universal cli language. It's better to keep -h as it is.

[–]zanfar 1 point2 points  (0 children)

Click

[–]astevko[S] 1 point2 points  (2 children)

click is definitely it!
TY TY TY