Hey! These docs are for version 2.0, which is no longer officially supported. Click here for the latest version, 2.7!
./pants lint [args]

Run all linters and/or formatters in check mode.

Config section: [lint]

Basic options

None

Advanced options

--[no-]lint-per-file-caching
PANTS_LINT_PER_FILE_CACHING
per_file_caching
default: False
Rather than linting all files in a single batch, lint each file as a separate process. Why do this? You'll get many more cache hits. Why not do this? Linters both have substantial startup overhead and are cheap to add one additional file to the run. On a cold cache, it is much faster to use `--no-per-file-caching`. We only recommend using `--per-file-caching` if you are using a remote cache or if you have benchmarked that this option will be faster than `--no-per-file-caching` for your use case.

--lint-reports-dir=<DIR>
PANTS_LINT_REPORTS_DIR
reports_dir
default: None
Specifying a directory causes linters that support writing report files to write into this directory.

Deprecated options

--[no-]lint-per-target-caching
PANTS_LINT_PER_TARGET_CACHING
per_target_caching
default: False
Deprecated, will be removed in version: 2.1.0.dev0
Use the renamed `--per-file-caching` option instead. If this option is set, Pants will now run per every file, rather than per target.
See `--per-file-caching`.

Related subsystems

bandit, black, docformatter, download-pex-bin, flake8, grpc_python_plugin, isort, lint, pex, protoc, pylint, python-infer, python-native-code, python-protobuf, python-repos, python-setup, source, subprocess-environment


Did this page help you?