Linter/formatter support is implemented in separate backends so that they are easy to opt in to individually:
pants.backend.python.lint.bandit: Supports the Bandit security issue detector.
pants.backend.python.lint.black: Supports the Black code formatter.
pants.backend.python.lint.docformatter: Supports the Docformatter docstring formatter.
pants.backend.python.lint.flake8: Supports the flake8 style checker.
pants.backend.python.lint.isort: Supports the isort import statement formatter.
pants.backend.python.lint.pylint: Supports the pylint style and error checker.
To enable linters/formatters, add the appropriate ones in
[GLOBAL] ... backend_packages = [ 'pants.backend.python', 'pants.backend.python.lint.black', 'pants.backend.python.lint.isort', ]
You'll now see
fmt goals in the output of
$ ./pants goals Goals ----- Use `./pants help $goal` to get help for a particular goal. ... fmt Autoformat source code. lint Run all linters and/or formatters in check mode. ...
How to activate MyPy
MyPy is run with the typecheck goal, rather than
Most of the formatters and linters allow you to configure
--version: the version to use.
--args: any command-line arguments you want to pass to the tool.
--extra-requirements: any additional libraries to install, such as any plugins.
--config: path to a config file; used if the file is in a non-standard location such that it cannot be auto-discovered.
[docformatter] args = ["--wrap-summaries=100", "--wrap-descriptions=100"] [flake8] # Load a config file in a non-standard location. config = "build-support/.flake8" version = "flake8==3.8.0" # Add a Flake8 plugin: extra_requirements.add = ["flake8-2020"]
./pants help-advanced black,
./pants help-advanced flake8, and so on for more information.
Config files are normally auto-discovered
For tools that autodiscover config files—such as Black, isort, Flake8, and Pylint—Pants will include any relevant config files in the process's sandbox when running the tool.
If your config file is in a non-standard location, you must instead set the
[isort].config. This will ensure that the config file is included in the process's sandbox and Pants will instruct the tool to load the config.
To temporarily skip a tool, use the
--skip option. For example, run:
$ ./pants --black-skip --flake8-skip lint ::
You can also skip on a per-target basis, which can be useful for incrementally adopting new tools. For example:
# Skip Black and Flake8 for all the non-test files in this folder. python_library(skip_black=True, skip_flake8=True) # Skip isort for all the test files in this folder. python_tests(name="tests", skip_isort=True)
When you run
./pants fmt :: and
./pants lint ::, Pants will ignore any files belonging to skipped targets.
With formatters and linters, there is usually no need to rerun on files that have not changed.
Use the option
--changed-since to get much better performance, like this:
$ ./pants --changed-since=HEAD fmt
$ ./pants --changed-since=main lint
Pants will find which files have changed and only run over those files. See Advanced target selection for more information.
./pants help-advanced pylint for instructions to add plugins written by you with the
If you want to write first-party plugins for other linters like Flake8, let us know on Slack.
Bandit output can be extremely verbose, including on successful runs. You may want to use its
--quiet option, which will turn off output for successful runs but keep it for failures.
For example, you can set this in your
[bandit] args = ["--quiet"]
Some Pants users had to explicitly set
default_section = "THIRDPARTY" to get iSort 5 to correctly classify their first-party imports, even though this is the default value.
They report that this config works for them:
# pyproject.toml [tool.isort] known_first_party = ["my_org"] default_section = "THIRDPARTY"
You may also want to try downgrading to iSort 4.x by setting
version = "isort>=4.6,<5" in the
[isort] options scope.
Updated 6 days ago