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
RFE: warn about disables using identifiers, promote symbolic names #3250
Comments
Hey @scop Thank you for creating an issue! We already support this pattern with
|
Oh, cool. However informational messages don't seem to cause a nonzero exit status, which I would like for this message. Is there a way to accomplish that? |
There isn't a way to accomplish this I'm afraid, other than promoting this check to a different category in |
Ok, filed #3251 for the confurability :) |
For the record, a colleague of mine (@xavfernandez) recently released a pylint plugin that registers such a warning message. The documentation is a bit short for now, but basically one just needs to:
And you get the following warnings:
|
I did not know about Since then, I've opened #3363 and its patch-plugin pylint-strict-informational so this becomes:
|
Very nice, thanks! |
Is your feature request related to a problem? Please describe
Would be nice to have a way to pylint emit warnings for
pylint disable=...
lines that use message identifiers as opposed to their symbolic names in code. The symbolic names can mostly be just understood when reading related code, whereas identifiers require one to look them up.Describe the solution you'd like
A warning message if one uses for example
# pylint disable=W0612
containing a suggestion to usedisable=unused-variable
instead.Additional context
I think I can have a look at implementing this sometime unless someone beats me to it, but posting this RFE to probe acceptability/desirability first.
The text was updated successfully, but these errors were encountered: