setuptools
Python setuptools, used to package python_distribution
targets.
Backend: pants.backend.python
Config section: [setuptools]
Basic options
None
Advanced options
extra_requirements
--setuptools-extra-requirements="['<str>', '<str>', ...]"
PANTS_SETUPTOOLS_EXTRA_REQUIREMENTS
[setuptools]
extra_requirements = [
'<str>',
'<str>',
...,
]
[ "wheel>=0.35.1,<0.38" ]
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.
lockfile
--setuptools-lockfile=<str>
PANTS_SETUPTOOLS_LOCKFILE
[setuptools]
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/subsystems/setuptools_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=setuptools
.
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
--setuptools-version=<str>
PANTS_SETUPTOOLS_VERSION
[setuptools]
version = <str>
setuptools>=50.3.0,<58.0
Requirement string for the tool.
Deprecated options
None
Related subsystems
None