In Pylint 0.21.1 (if it matters: astng 0.20.1, common 0.50.3, and Python 2.6.6 (r266:84292, Sep 15 2010, 16:22:56), I’m trying to disable warning C0321 (“more than one statement on a single line” — I frequently put if statements with short single-line results on the same line), I’m trying to disable warning C0321 (“more than one statement on a single line” — I often put if statements
I tried including disable=C0321 in the Pylint configuration file, but Pylint still reports it. Variations on that line (such as disable=0321 or disable=C321) are noted as errors, indicating that Pylint understands the option. It’s merely a case of ignoring it.
Is this a Pylint problem, or am I making a mistake? Is there a way to get out of this?
I’d like to get rid of some of this background noise.
Asked by Head Geek
The output of pylint —generate-rcfile is as follows:
[MESSAGES CONTROL] # Enable the message, report, category or checker with the given id(s). You can # either give multiple identifier separated by comma (,) or put this option # multiple time. #enable= # Disable the message, report, category or checker with the given id(s). You # can either give multiple identifier separated by comma (,) or put this option # multiple time (only on the command line, not in the configuration file where # it should appear only once). #disable=
So it appears that the disable= line/s should be inside a section [MESSAGES CONTROL] in your /.pylintrc.
Answered by Chris Morgan
I ran into this issue when using Eclipse and came up with the following solution:
Hold Shift, right-click, and choose to open the windows command in the pylint folder (e.g. C:Python26Libsite-packagespylint). Type:
lint.py --generate-rcfile > standard.rc
The standard.rc configuration file is created as a result of this. Open it in Notepad and uncomment disable= and add the message IDs you want to disable under [MESSAGES CONTROL], for example:
Save the file, and in the parameters box in Eclipse Window Preferences PyDev *pylint, type:
It should now work…
You can also include a note at the top of your code that Pylint will read:
# pylint: disable=C0321
Pylint message codes.
—disable-ids=C0321 in the arguments box, for example, does not function.
The dictionary _messages, a property of an instance of the pylint.utils.MessagesHandlerMixIn class, stores all accessible Pylint messages. This dictionary is initially empty when Pylint is launched with the argument —disable-ids=… (at least without a configuration file), resulting in a KeyError exception in Pylint (pylint.utils.MessagesHandlerMixIn.check message id) ().
This error message can be found on the Pylint Console in Eclipse (windows* show view Console, select Pylint console from the console options besides the console icon.)
Answered by Remi
Starting from Pylint v. 0.25.3, you can use the symbolic names for disabling warnings instead of having to remember all those code numbers. E.g.:
# pylint: disable=locally-disabled, multiple-statements, fixme, line-too-long
This style is more instructive than cryptic error codes, and also more practical since newer versions of Pylint only output the symbolic name, not the error code.
This is where you’ll find the relationship between symbolic names and codes.
A disable comment can be placed on its own line, causing everything after it in the same block to be disabled. It can also be added at the end of the line to which it is intended to apply.
If Pylint generates “Locally disabling” messages, use the disable locally-disabled command first, as shown in the example above.
Answered by imolit
To disable a warning in a block locally, add
# pylint: disable=C0321
to that block.
Answered by thakis
Pylint’s warnings and faults can be turned off in a number of ways. Which one to use depends on whether you want the disablement to be applied worldwide or locally, which is an essential design decision.
This goes beyond Chris Morgan’s description of the /.pylintrc file (in your $HOME directory). Pylint will look for rc files, with a priority system that prioritizes “closer” files:
The majority of these files are named pylintrc, with the exception of the file in having a leading dot.
Add lines to your pylintrc file to disable specific pylint messages. Consider the following scenario:
[MESSAGES CONTROL] disable=locally-disabled
The # pylint syntax is used to disable a single line, whereas the # pragma pylint syntax is used to disable this line and subsequent lines. It’s easy to get these mixed up, especially when copying and pasting.
Putting Everything Together
I normally use a combination of these methods.
You can behave at several levels of indirection in Python, just like everything else. My advise is to consider what belongs at what level so you don’t end up with a Pylint policy that is excessively permissive.
Answered by Chris Johnson
Post is based on https://stackoverflow.com/questions/4341746/how-do-i-disable-a-pylint-warning