Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You can use a <strong><code>~/.pylintrc</code></strong> file to configure Pylint - amongst other things, this allows you to ignore warnings you don't care about. If you must use tabs, tell Pylint by setting the <code>indent-string</code> option to the tab character:</p> <pre><code>[FORMAT] indent-string=\t </code></pre> <p>Pylint then will only warn you about places where you <em>mix</em> tabs and spaces - which you should never do, and keep an eye on in your code.</p> <p>To disable other warnings, use <a href="http://docs.pylint.org/faq.html#message-control" rel="noreferrer">Message Control</a> to turn them off individually:</p> <pre><code>[MESSAGES CONTROL] # C0111: Missing docstring # R0904: Too many public methods disable=C0111,R0904 </code></pre> <p>For getting the IDs for the messages you're interested in, look at the "MESSAGES" section of your Pylint report, or see <a href="http://pylint-messages.wikidot.com/all-codes" rel="noreferrer">http://pylint-messages.wikidot.com/all-codes</a>.</p> <p>Also see the <a href="http://docs.pylint.org/faq.html#message-control" rel="noreferrer">Message Control</a> section in the Pylint docs, and the respective FAQ entry on <a href="http://docs.pylint.org/faq.html#how-do-i-find-the-option-name-for-pylintrc-corresponding-to-a-specific-command-line-option" rel="noreferrer">How to find the option name for <code>.pylintrc</code> corresponding to a specific command line option</a>.</p> <p>I'd really recommend to use a <code>.pylintrc</code>, but for the sake of completeness, your other options are:</p> <ul> <li>annotate your sourcecode with <a href="http://docs.pylint.org/faq.html#is-it-possible-to-locally-disable-a-particular-message" rel="noreferrer">hint comments</a> for Pylint, e.g. <code>#pylint: disable=W0123,E4567</code></li> <li>call pylint with the respective command line options, e.g. <code>pylint --disable=W0702,C0103</code></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload