Skip to content

Conversation

@jonafato
Copy link
Contributor

@jonafato jonafato commented Dec 2, 2015

Revert changes made to BadOptionUsage.__init__ in 5f98f57. Additionally, store option_name on the exception instance to allow programmatic access to it (this matches the behavior of several other exceptions) and document the param in BadOptionUsage's docstring. Fixes #474.

Revert changes made to ``BadOptionUsage.__init__`` in
5f98f57. Additionally, store
``option_name`` on the exception instance to allow programmatic access
to it (this matches the behavior of several other exceptions) and
document the param in ``BadOptionUsage``'s docstring. Fixes #474.
mitsuhiko added a commit that referenced this pull request Dec 3, 2015
Restore option_name parameter to BadOptionUsage
@mitsuhiko mitsuhiko merged commit 79e80fe into pallets:master Dec 3, 2015
@jonafato jonafato deleted the restore-option_name branch December 3, 2015 17:33
@ael-code
Copy link

So the versions that accepts only two parameters instead of three are 6.0, 6.1, 6.2

ael-code added a commit to ael-code/libreant that referenced this pull request Mar 12, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BadOptionUsage exception no longer takes option_name argument

3 participants