Skip to main content
Version: 2.12 (deprecated)

autoflake

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

Backend: pants.backend.experimental.python.lint.autoflake

Config section: [autoflake]

Basic options​

args​

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

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

export​

--[no-]autoflake-export
PANTS_AUTOFLAKE_EXPORT
pants.toml
[autoflake]
export = <bool>
default: True

If true, export a virtual environment with Autoflake when running /home/josh/work/scie-pants/dist/pants export.

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

skip​

--[no-]autoflake-skip
PANTS_AUTOFLAKE_SKIP
pants.toml
[autoflake]
skip = <bool>
default: False

Don't use Autoflake when running /home/josh/work/scie-pants/dist/pants fmt and /home/josh/work/scie-pants/dist/pants lint.

Advanced options​

console_script​

--autoflake-console-script=<str>
PANTS_AUTOFLAKE_CONSOLE_SCRIPT
pants.toml
[autoflake]
console_script = <str>
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
pants.toml
[autoflake]
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_requirements​

--autoflake-extra-requirements="['<str>', '<str>', ...]"
PANTS_AUTOFLAKE_EXTRA_REQUIREMENTS
pants.toml
[autoflake]
extra_requirements = [
    '<str>',
    '<str>',
    ...,
]
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
pants.toml
[autoflake]
interpreter_constraints = [
    '<str>',
    '<str>',
    ...,
]
default: 
[
  "CPython>=3.7,<4"
]

Python interpreter constraints for this tool.

lockfile​

--autoflake-lockfile=<str>
PANTS_AUTOFLAKE_LOCKFILE
pants.toml
[autoflake]
lockfile = <str>
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/autoflake/autoflake.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 /home/josh/work/scie-pants/dist/pants generate-lockfiles --resolve=autoflake.

As explained at https://www.pantsbuild.org/v2.12/docs/python-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.

version​

--autoflake-version=<str>
PANTS_AUTOFLAKE_VERSION
pants.toml
[autoflake]
version = <str>
default: autoflake==1.4

Requirement string for the tool.

Deprecated options​

None

None