yapf
A formatter for Python files (https://github.com/google/yapf).
Backend: pants.core
Config section: [yapf]
Basic options
args
--yapf-args="[<shell_str>, <shell_str>, ...]"
PANTS_YAPF_ARGS
[yapf]
args = [
<shell_str>,
<shell_str>,
...,
]
[]
Arguments to pass directly to yapf, e.g. --yapf-args="--no-local-style"
.
Certain arguments, specifically --recursive
, --in-place
, and --parallel
, will be ignored because Pants takes care of finding all the relevant files and running the formatting in parallel.
skip
--[no-]yapf-skip
PANTS_YAPF_SKIP
[yapf]
skip = <bool>
False
Don't use yapf when running /home/josh/work/scie-pants/dist/pants fmt
and /home/josh/work/scie-pants/dist/pants lint
.
Advanced options
config
--yapf-config=<file_option>
PANTS_YAPF_CONFIG
[yapf]
config = <file_option>
None
Path to style file understood by yapf (https://github.com/google/yapf#formatting-style/).
Setting this option will disable [yapf].config_discovery
. Use this option if the config is located in a non-standard location.
config_discovery
--[no-]yapf-config-discovery
PANTS_YAPF_CONFIG_DISCOVERY
[yapf]
config_discovery = <bool>
True
If true, Pants will include any relevant config files during runs (.style.yapf
, pyproject.toml
, and setup.cfg
).
Use [yapf].config
instead if your config is in a non-standard location.
console_script
--yapf-console-script=<str>
PANTS_YAPF_CONSOLE_SCRIPT
[yapf]
console_script = <str>
yapf
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
--yapf-entry-point=<str>
PANTS_YAPF_ENTRY_POINT
[yapf]
entry_point = <str>
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_requirements
--yapf-extra-requirements="['<str>', '<str>', ...]"
PANTS_YAPF_EXTRA_REQUIREMENTS
[yapf]
extra_requirements = [
'<str>',
'<str>',
...,
]
[ "toml" ]
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
--yapf-interpreter-constraints="['<str>', '<str>', ...]"
PANTS_YAPF_INTERPRETER_CONSTRAINTS
[yapf]
interpreter_constraints = [
'<str>',
'<str>',
...,
]
[ "CPython>=3.6" ]
Python interpreter constraints for this tool.
lockfile
--yapf-lockfile=<str>
PANTS_YAPF_LOCKFILE
[yapf]
lockfile = <str>
<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.10.1/src/python/pants/backend/python/lint/yapf/lockfile.txt 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=yapf
.
Lockfile generation currently does not wire up the [python-repos]
options. If lockfile generation fails, you can manually generate a lockfile, such as by using pip-compile or pip freeze
. Set this option to the path to your manually generated lockfile. When manually maintaining lockfiles, set [python].invalid_lockfile_behavior = 'ignore'
.
version
--yapf-version=<str>
PANTS_YAPF_VERSION
[yapf]
version = <str>
yapf==0.32.0
Requirement string for the tool.
Deprecated options
None
Related subsystems
None