-
Notifications
You must be signed in to change notification settings - Fork 494
BUG: Use return codes properly, add --count #1558
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
Conversation
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few initial comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some more comments.
Also I wonder if given the exit and count behaviour changes, and some of the other changes that have gone in recently, whether the next release should be a major version bump?
If using semver it should be a major as it’s a breaking API change |
Okay to merge now that all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Do you want to see if @craigbarnes has further feedback or @vinc17fr has any. Also as @kkirsche and I both commented, please can we bump the major version in this PR. |
Done |
LGTM. |
Use standard return codes:
264
instead of1
for bad usage165
when there are spelling errors--count
to print to the last line ofstderr
the number of errors (likeflake8
); should allow easy-ish fixes for people who actually want the countAdds a wrapper to our tests that goes and grabs the
capsys
output from one stack frame higher so that a ton of lines didn't have to change.Closes #1495.
@vinc17fr @craigbarnes @kkirsche WDYT?