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

How to handle option conflicts? #38

Open
clagraff opened this issue Dec 7, 2016 · 0 comments
Open

How to handle option conflicts? #38

clagraff opened this issue Dec 7, 2016 · 0 comments
Labels

Comments

@clagraff
Copy link
Owner

clagraff commented Dec 7, 2016

Inspired by: https://docs.python.org/dev/library/argparse.html#conflict-handler

If two options are added to the parser which share the same name, how should the conflict be handled? Currently, they will override each other such that the last option added is the option that will exist.

Is this ideal? Python allows for the option to attempt to "resolve" such conflicts. Personally, I don't think I want to support this.
I could potentially see either keeping with how the library currently overrides duplicated options; or, panic when a duplicated option name is used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant