Skip to main content
Version: 2.25 (dev)

flake8

The Flake8 Python linter (https://flake8.pycqa.org/).

This version of Pants uses flake8 version 5.0.4 by default. Use a dedicated lockfile and the install_from_resolve option to control this.

Backend: pants.backend.python.lint.flake8

Config section: [flake8]

Basic options​

args​

--flake8-args="[<shell_str>, <shell_str>, ...]"
PANTS_FLAKE8_ARGS
pants.toml
[flake8]
args = [
    <shell_str>,
    <shell_str>,
    ...,
]
default: []

Arguments to pass directly to Flake8, e.g. --flake8-args='--ignore E123,W456 --enable-extensions H111'.

skip​

--[no-]flake8-skip
PANTS_FLAKE8_SKIP
pants.toml
[flake8]
skip = <bool>
default: False

If true, don't use Flake8 when running pants lint.

Advanced options​

config​

--flake8-config=<file_option>
PANTS_FLAKE8_CONFIG
pants.toml
[flake8]
config = <file_option>
default: None

Path to an INI config file understood by Flake8 (https://flake8.pycqa.org/en/latest/user/configuration.html).

Setting this option will disable [flake8].config_discovery. Use this option if the config is located in a non-standard location.

config_discovery​

--[no-]flake8-config-discovery
PANTS_FLAKE8_CONFIG_DISCOVERY
pants.toml
[flake8]
config_discovery = <bool>
default: True

If true, Pants will include any relevant config files during runs (.flake8, flake8, setup.cfg, and tox.ini).

Use [flake8].config instead if your config is in a non-standard location.

console_script​

--flake8-console-script=<str>
PANTS_FLAKE8_CONSOLE_SCRIPT
pants.toml
[flake8]
console_script = <str>
default: flake8

The console script for the tool. Using this option is generally preferable to (and mutually exclusive with) specifying an --entry-point since console script names have a higher expectation of staying stable across releases of the tool. Usually, you will not want to change this from the default.

entry_point​

--flake8-entry-point=<str>
PANTS_FLAKE8_ENTRY_POINT
pants.toml
[flake8]
entry_point = <str>
default: None

The entry point for the tool. Generally you only want to use this option if the tool does not offer a --console-script (which this option is mutually exclusive with). Usually, you will not want to change this from the default.

extra_files​

--flake8-extra-files="[<file_option>, <file_option>, ...]"
PANTS_FLAKE8_EXTRA_FILES
pants.toml
[flake8]
extra_files = [
    <file_option>,
    <file_option>,
    ...,
]
default: []

Paths to extra files to include in the sandbox. This can be useful for Flake8 plugins, like including config files for the flake8-bandit plugin.

install_from_resolve​

--flake8-install-from-resolve=<str>
PANTS_FLAKE8_INSTALL_FROM_RESOLVE
pants.toml
[flake8]
install_from_resolve = <str>
default: None

If specified, install the tool using the lockfile for this named resolve.

This resolve must be defined in [python].resolves, as described in https://www.pantsbuild.org/2.24/docs/python/overview/lockfiles#lockfiles-for-tools.

The resolve's entire lockfile will be installed, unless specific requirements are listed via the requirements option, in which case only those requirements will be installed. This is useful if you don't want to invalidate the tool's outputs when the resolve incurs changes to unrelated requirements.

If unspecified, and the lockfile option is unset, the tool will be installed using the default lockfile shipped with Pants, which uses flake8 version 5.0.4.

If unspecified, and the lockfile option is set, the tool will use the custom flake8 "tool lockfile" generated from the version and extra_requirements options. But note that this mechanism is deprecated.

requirements​

--flake8-requirements="['<str>', '<str>', ...]"
PANTS_FLAKE8_REQUIREMENTS
pants.toml
[flake8]
requirements = [
    '<str>',
    '<str>',
    ...,
]
default: []

If install_from_resolve is specified, install these requirements, at the versions provided by the specified resolve's lockfile.

Values can be pip-style requirements (e.g., tool or tool==1.2.3 or tool>=1.2.3), or addresses of python_requirement targets (or targets that generate or depend on python_requirement targets). Make sure to use the // prefix to refer to targets using their full address from the root (e.g. //3rdparty/python:tool). This is necessary to distinguish address specs from local or VCS requirements.

The lockfile will be validated against the requirements - if a lockfile doesn't provide the requirement (at a suitable version, if the requirement specifies version constraints) Pants will error.

If unspecified, install the entire lockfile.

source_plugins​

--flake8-source-plugins="[<target_option>, <target_option>, ...]"
PANTS_FLAKE8_SOURCE_PLUGINS
pants.toml
[flake8]
source_plugins = [
    <target_option>,
    <target_option>,
    ...,
]
default: []

An optional list of python_sources target addresses to load first-party plugins.

You must set the plugin's parent directory as a source root. For example, if your plugin is at build-support/flake8/custom_plugin.py, add 'build-support/flake8' to [source].root_patterns in pants.toml. This is necessary for Pants to know how to tell Flake8 to discover your plugin. See https://www.pantsbuild.org/2.24/docs/using-pants/key-concepts/source-roots

You must also set [flake8:local-plugins] in your Flake8 config file.

For example:

[flake8:local-plugins]
extension =
CUSTOMCODE = custom_plugin:MyChecker

While your plugin's code can depend on other first-party code and third-party requirements, all first-party dependencies of the plugin must live in the same directory or a subdirectory.

To instead load third-party plugins, add them to a custom resolve alongside flake8 itself, as described in https://www.pantsbuild.org/2.24/docs/python/overview/lockfiles#lockfiles-for-tools.

Deprecated options​

None

None