HomeDocs
DocsCommunityTestimonialsUsersGitHubTwitterBlogJobsTermsPrivacyCookies
TermsPrivacyCookies
Hey! These docs are for version 2.10, which is no longer officially supported. Click here for the latest version, 2.18!

autoflake

The Autoflake Python code formatter (https://github.com/myint/autoflake).

Backend: pants.backend.experimental.python.lint.autoflake
Config section: [autoflake]

Basic options

skip

--[no-]autoflake-skip
PANTS_AUTOFLAKE_SKIP
default: False

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


args

--autoflake-args="[<shell_str>, <shell_str>, ...]"
PANTS_AUTOFLAKE_ARGS
default: []

Arguments to pass directly to Autoflake, e.g. --autoflake-args="--target-version=py37 --quiet"


Advanced options

version

--autoflake-version=<str>
PANTS_AUTOFLAKE_VERSION
default: autoflake==1.4

Requirement string for the tool.


extra_requirements

--autoflake-extra-requirements="['<str>', '<str>', ...]"
PANTS_AUTOFLAKE_EXTRA_REQUIREMENTS
default: []

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

--autoflake-interpreter-constraints="['<str>', '<str>', ...]"
PANTS_AUTOFLAKE_INTERPRETER_CONSTRAINTS
default:
[
  "CPython>=3.7,<4"
]

Python interpreter constraints for this tool.


lockfile

--autoflake-lockfile=<str>
PANTS_AUTOFLAKE_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.10.1rc1/src/python/pants/backend/python/lint/autoflake/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=autoflake.

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'.


console_script

--autoflake-console-script=<str>
PANTS_AUTOFLAKE_CONSOLE_SCRIPT
default: autoflake

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

--autoflake-entry-point=<str>
PANTS_AUTOFLAKE_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.


Deprecated options

None