pylint #110235 Support comments after message-control pragmas [open]
My code now contains a lot of message-control pragmas (e.g. #pylint: disable=X0123). It isn't always immediately clear what message the message id corresponds to. Even if you do look it up, it may not be clear why the message has been disabled (rather than fixed).
It would be nice to be able to add a comment comment, inline with the message-control pragma - perhaps like this example:
def callback( old_value, #pylint: disable=W0613 # Unused, but must be present to match expected signature. new_value, ): print "The value has changed to", new_value
At the moment, Pylint (0.25.2) rejects this, and ignores the initial pragma.
|done in||<not specified>|
|closed by||<not specified>|
- pylint #4288 message [en|dis]abling refactoring
- logilab-astng #903 cache for external libraries
- pylint #3212 re-enable all warnings from the command line
- pylint #4983 new py2.5 check: test "yield" in "try" body with yield in exception handlers.
- pylint #17958 pylint -e must not silence Fatal messages