black

The Black Python code formatter (https://black.readthedocs.io/).

Backend: pants.core
Config section: [black]

Basic options

`skip`

--[no-]black-skip
PANTS_BLACK_SKIP

default: False

Don't use Black when running ./pants fmt and ./pants lint.

`args`

--black-args="[<shell_str>, <shell_str>, ...]"
PANTS_BLACK_ARGS

default: []

Arguments to pass directly to Black, e.g. --black-args='--target-version=py37 --quiet'.

`export`

--[no-]black-export
PANTS_BLACK_EXPORT

default: True

If true, export a virtual environment with Black when running ./pants export.

This can be useful, for example, with IDE integrations to point your editor to the tool's binary.

Advanced options

`version`

--black-version=<str>
PANTS_BLACK_VERSION

default: black==22.1.0

Requirement string for the tool.

`extra_requirements`

--black-extra-requirements="['<str>', '<str>', ...]"
PANTS_BLACK_EXTRA_REQUIREMENTS

default:

[
  "typing-extensions>=3.10.0.0; python_version < \"3.10\""
]

Any additional requirement strings to use with the tool. This is useful if the tool allows you to install plugins or if you need to constrain a dependency to a certain version.

`interpreter_constraints`

--black-interpreter-constraints="['<str>', '<str>', ...]"
PANTS_BLACK_INTERPRETER_CONSTRAINTS

default:

[
  "CPython>=3.7,<4"
]

Python interpreter constraints for this tool.

`lockfile`

--black-lockfile=<str>
PANTS_BLACK_LOCKFILE

default: <default>

Path to a lockfile used for installing the tool.

Set to the string <default> to use a lockfile provided by Pants, so long as you have not changed the --version and --extra-requirements options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by [python].invalid_lockfile_behavior). See https://github.com/pantsbuild/pants/blob/release_2.12.1/src/python/pants/backend/python/lint/black/black.lock for the default lockfile contents.

Set to the string <none> to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.

To use a custom lockfile, set this option to a file path relative to the build root, then run ./pants generate-lockfiles --resolve=black.

As explained at Third-party dependencies, lockfile generation via generate-lockfiles does not always work and you may want to manually generate the lockfile. You will want to set [python].invalid_lockfile_behavior = 'ignore' so that Pants does not complain about missing lockfile headers.

`console_script`

--black-console-script=<str>
PANTS_BLACK_CONSOLE_SCRIPT

default: black

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`

--black-entry-point=<str>
PANTS_BLACK_ENTRY_POINT

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.

`config`

--black-config=<file_option>
PANTS_BLACK_CONFIG

default: None

Path to a TOML config file understood by Black (https://github.com/psf/black#configuration-format).

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

`config_discovery`

--[no-]black-config-discovery
PANTS_BLACK_CONFIG_DISCOVERY

default: True

If true, Pants will include any relevant pyproject.toml config files during runs.

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

Deprecated options

None