Skip to main content
Version: 2.21 (deprecated)

pyupgrade

Upgrade syntax for newer versions of the language (https://github.com/asottile/pyupgrade).

Backend: pants.backend.python.lint.pyupgrade

Config section: [pyupgrade]

Basic options​

args​

--pyupgrade-args="[<shell_str>, <shell_str>, ...]"
PANTS_PYUPGRADE_ARGS
pants.toml
[pyupgrade]
args = [
    <shell_str>,
    <shell_str>,
    ...,
]
default: []

Arguments to pass directly to pyupgrade, e.g. --pyupgrade-args='--py39-plus --keep-runtime-typing'.

skip​

--[no-]pyupgrade-skip
PANTS_PYUPGRADE_SKIP
pants.toml
[pyupgrade]
skip = <bool>
default: False

If true, don't use pyupgrade when running pants fmt and pants lint.

Advanced options​

console_script​

--pyupgrade-console-script=<str>
PANTS_PYUPGRADE_CONSOLE_SCRIPT
pants.toml
[pyupgrade]
console_script = <str>
default: pyupgrade

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​

--pyupgrade-entry-point=<str>
PANTS_PYUPGRADE_ENTRY_POINT
pants.toml
[pyupgrade]
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.

install_from_resolve​

--pyupgrade-install-from-resolve=<str>
PANTS_PYUPGRADE_INSTALL_FROM_RESOLVE
pants.toml
[pyupgrade]
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.21/docs/python/overview/third-party-dependencies#user-lockfiles.

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.

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

interpreter_constraints​

--pyupgrade-interpreter-constraints="['<str>', '<str>', ...]"
PANTS_PYUPGRADE_INTERPRETER_CONSTRAINTS
pants.toml
[pyupgrade]
interpreter_constraints = [
    '<str>',
    '<str>',
    ...,
]
default: 
[
  "CPython>=3.7,<4"
]

Python interpreter constraints for this tool.

requirements​

--pyupgrade-requirements="['<str>', '<str>', ...]"
PANTS_PYUPGRADE_REQUIREMENTS
pants.toml
[pyupgrade]
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).

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.

Deprecated options​

None

None