1. Prospector - Python Static Analysis¶
Prospector is a tool to analyse Python code and output information about errors, potential problems, convention violations and complexity.
It brings together the functionality of other Python analysis tools such as Pylint, pycodestyle, and McCabe complexity. See the Supported Tools section for a complete list of default and optional extra tools.
The primary aim of Prospector is to be useful ‘out of the box’. A common complaint of other Python analysis tools is that it takes a long time to filter through which errors are relevant or interesting to your own coding style. Prospector provides some default profiles, which hopefully will provide a good starting point and will be useful straight away, and adapts the output depending on the libraries your project uses.
You can install default tools using
pip install prospector
For a full list of optional extra tools, and specific examples to install each of them, see the page on supported tools.
For example to install an optional tool such as
pip install prospector[with_pyroma]
Some shells (such as
Zsh, the default shell of macOS Catalina) require brackets to be escaped:
pip install prospector\[with_pyroma\]
To install two or more optional extra tools at the same time, they must be comma separated (and without spaces). For example to install mypy and bandit:
pip install prospector[with_mypy,with_bandit]
And to install all optional extra tools at the same time, install prospector using the
pip install prospector[with_everything]
For best results, you should install prospector to the same place as your project and its dependencies. That is, if you are using virtual environments, install prospector into that virtual environment alongside your code. This allows the underlying tools to give better results, as they can infer and use knowledge of libraries that you use. If you install prospector system-wide and use it on a project in a virtual environment, you will see several incorrect errors because prospector cannot access the libraries your project uses.
Simply run prospector from the root of your project:
This will output a list of messages pointing out potential problems or errors, for example:
L5:0 ToolBase: pylint - R0922
Abstract class is only referenced 1 times
Read about the full list of options in the usage page.
It is also possible to use prospector as a pre-commit hook.
Adapting to Dependencies¶
Prospector will try to detect the libraries that your project uses, and adapt the output and filtering to those libraries. For example, if you use Django, the pylint-django plugin will be loaded to help Pylint inspect Django-specific code.
There is currently support for the following frameworks:
Prospector can be configured to be more or less strict. The more strict, the more errors and warnings it will find. At higher strictness levels, you may find that the output is a bit too picky. The default level is designed to give useful output and warnings but also to suppress messages which are not necessarily useful.
To change the strictness level:
prospector --strictness high
Valid levels are
A profile is a YAML file containing various directives about which messages and which tools to allow or disable. Profiles can inherit from each other, allowing you to adapt the behaviour of existing profiles or compose several smaller specialised profiles into one to suit your project.
Note that the ‘strictness’ is implemented as a profile.
There is more detail about profiles and how to use them on the profiles documentation page.
Prospector can be configured as a pre-commit hook.
For more information see the pre-commit documentation.
Prospector is available under the GPLv2 License.