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
Add --strict option to fail on informational messages #3363
Comments
In the meantime, a fake plugin pylint-strict-informational that does exactly that has been published. To use, |
A strict mode could make sense for other checks as well. It's definitely something we should consider. |
@xavfernandez Unfortunately I ended up with the following workaround (executed before calling find .venv/lib -path '*/pylint/constants.py' -exec sed -r -i -e 's@(^MSG_TYPES_STATUS = .*):\s*0,(.*)@\1: 4,\2 # monkey-patched, waiting for pylint#3363@g' {} ';' |
Note, since ab094ae, it is not just enough to change the This is the reason that pylint-strict-informational no longer works (unless you use an option like |
Hello @Pierre-Sassoulas and everyone, sorry to take long, but: why was this issue closed? PR #4713 does not seem to add a flag to allow failing on any informational message. At least it seems I can now achieve it by manually adding |
Never mind, adding the following to my
|
Is your feature request related to a problem? Please describe
A bunch of useful informational messages exist in pylint but enforcing them in CI is tricky since their presence doesn't affect the exit code.
Describe the solution you'd like
The activation of this
--strict
(or--fail-on-informational
) option would simply changeMSG_TYPES_STATUS['I']
value to a none-zero value to be determined (I'd go with 1)https://github.com/PyCQA/pylint/blob/f2f4e6f42416644471ab003d4df7ecf052c3c411/pylint/constants.py#L33
to make pylint fail when an informational message is produced.
Additional context
This could be an alternative to #3251
The text was updated successfully, but these errors were encountered: