The Static Code Analysis pane detects style issues, bad practices, potential bugs, and other quality problems in your code, all without having to actually execute it.
Spyder’s static analyzer is powered by the best in class Pylint back-end, which can intelligently detect an enormous and customizable range of problem signatures.
You can select the desired file to analyze directly in the Editor by clicking anywhere within it, or you can manually enter the Python module or package path you’d like it to check in the path entry textbox in the Static Code Analysis pane.
The analyzer works with both .py (or .pyw) Python scripts and whole Python packages (directories containing an __init__.py file).
Then, to run it, select Source ‣ Run static code analysis from the menubar, click the Analyze button in the pane, or press the configurable static analysis shortcut (F8 by default).
Cancel analyzing a file with the Stop button, and if analysis fails, click the Output button to find out why.
To go directly to the file and line in the Editor highlighted by a failed check, just click its name.
You can click the dropdown or press the Down Arrow key in the filename field to view results of previous analyses; the number of recent runs Spyder should remember can be customized in the History dialog from the Static Code Analysis context menu.
All standard checks are run by default.
You can turn certain messages off at the line, block or file/module level by adding a # pylint: disable=<list of message names> comment at the respective level, where the <...> portion should be replaced with a comma-separated list (or single value) without the </> of Pylint message names (e.g. multiple-statements, or fixme, line-too-long; you can also use error codes like C0321 although names are preferred for clarity).
Or, you can globally suppress certain messages by editing the .pylintrc configuration file in your user home directory.
For more details on configuring Pylint, see the Pylint documentation.
# pylint: disable=<list of message names>