mypy-protobuf

version

--mypy-protobuf-version=<str>

PANTS_MYPY_PROTOBUF_VERSION

Requirement string for the tool.

extra_requirements

--mypy-protobuf-extra-requirements="['<str>', '<str>', ...]"

PANTS_MYPY_PROTOBUF_EXTRA_REQUIREMENTS

[
  "protobuf<3.21"
]

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

--mypy-protobuf-interpreter-constraints="['<str>', '<str>', ...]"

PANTS_MYPY_PROTOBUF_INTERPRETER_CONSTRAINTS

[
  "CPython>=3.7,<4"
]

Python interpreter constraints for this tool.

lockfile

--mypy-protobuf-lockfile=<str>

PANTS_MYPY_PROTOBUF_LOCKFILE

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.15.1rc2/src/python/pants/backend/codegen/protobuf/python/mypy_protobuf.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 and supply-chain security.

To use a custom lockfile, set this option to a file path relative to the build root, then run pants generate-lockfiles --resolve=mypy-protobuf.

Alternatively, you can set this option to the path to a custom lockfile using pip's requirements.txt-style, ideally with --hash. Set [python].invalid_lockfile_behavior = 'ignore' so that Pants does not complain about missing lockfile headers.