-
Notifications
You must be signed in to change notification settings - Fork 45
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
Version 0.6 changed behavior with unknown arguments #29
Comments
DannyBen
added a commit
to DannyBen/madness
that referenced
this issue
Apr 7, 2017
Ah right, that's not intended - I guess that part is not covered in the tests |
@ryanartecona were those errors removed intentionally? |
Not intentionally as far as I remember.
On Fri, Apr 7, 2017 at 8:19 PM Alex Speller ***@***.***> wrote:
@ryanartecona <https://github.com/ryanartecona> were those errors removed
intentionally?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA2Uh5PH3kkR3Fh5i6v0sd4v6m6k53nSks5rtuC3gaJpZM4M2ntl>
.
--
Ryan Artecona
|
Any chance of bringing it back to the original behavior soon (as in 0.6.1)? |
Ahm.... bump? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Although I am happy to see a new 0..6 version, it introduces what I assume is an unintended behavior.
With the previous 0.5 version, when running the command with an unrecognized argument, docopt would output something like:
With the new version, it does not output the error line, only the usage.
I see the last merge removed this line from a couple of places
The text was updated successfully, but these errors were encountered: