A tool for turning .pex files into Function-as-a-Service artifacts (https://github.com/pantsbuild/lambdex).

Backend: pants.backend.awslambda.python
Config section: [lambdex]

Basic options

None

Advanced options

version

--lambdex-version=<str>
PANTS_LAMBDEX_VERSION
default: lambdex==0.1.6

Requirement string for the tool.


extra_requirements

--lambdex-extra-requirements="['<str>', '<str>', ...]"
PANTS_LAMBDEX_EXTRA_REQUIREMENTS
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

--lambdex-interpreter-constraints="['<str>', '<str>', ...]"
PANTS_LAMBDEX_INTERPRETER_CONSTRAINTS
default:
[
  "CPython>=3.7,<3.10"
]

Python interpreter constraints for this tool.


lockfile

--lambdex-lockfile=<str>
PANTS_LAMBDEX_LOCKFILE
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.11.1rc2/src/python/pants/backend/python/subsystems/lambdex.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 ./pants generate-lockfiles --resolve=lambdex.

As explained at 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.


console_script

--lambdex-console-script=<str>
PANTS_LAMBDEX_CONSOLE_SCRIPT
default: lambdex

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

--lambdex-entry-point=<str>
PANTS_LAMBDEX_ENTRY_POINT
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.


Deprecated options

None


Did this page help you?