generate-lockfiles

./pants generate-lockfiles [args]

Generate lockfiles for Python third-party dependencies.

Config section: [generate-lockfiles]

Basic options

resolve

--generate-lockfiles-resolve="['<str>', '<str>', ...]"
PANTS_GENERATE_LOCKFILES_RESOLVE
default: []

Only generate lockfiles for the specified resolve(s).

For now, resolves are the options scope for each Python tool that supports lockfiles, such as black, pytest, and mypy-protobuf. For example, you can run ./pants generate-lockfiles --resolve=black --resolve=pytest to only generate the lockfile for those two tools.

If you specify an invalid resolve name, like 'fake', Pants will output all possible values.

If not specified, Pants will generate for all resolves.


Advanced options

custom_command

--generate-lockfiles-custom-command=<str>
PANTS_GENERATE_LOCKFILES_CUSTOM_COMMAND
default: None

If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running ./pants generate-lockfiles --resolve=<name> like normal.


Deprecated options

None

Related subsystems

bandit, black, coverage-py, docformatter, download-pex-bin, flake8, generate-lockfiles, grpc-python-plugin, ipython, isort, lambdex, mypy, mypy-protobuf, pex, poetry, protoc, pylint, pytest, python-infer, python-native-code, python-protobuf, python-repos, python-setup, setuptools, shell-setup, shellcheck, source, subprocess-environment, yapf


Did this page help you?