The PEX (Python EXecutable) tool (https://github.com/pantsbuild/pex).
Backend: <span style="color: purple"><code>pants.core</code></span> Config section: <span style="color: purple"><code>[pex-cli]</code></span>
## Basic options
None
## Advanced options
<div style="color: purple">
### `version`
<code>--pex-cli-version=<str></code><br> <code>PANTS_PEX_CLI_VERSION</code><br>
</div> <div style="padding-left: 2em;"> <span style="color: green">default: <code>v2.1.108</code></span>
<br>
Use this version of pex.
Supported pex versions: >=2.1.108,<3.0
</div> <br>
<div style="color: purple">
### `known_versions`
<code>--pex-cli-known-versions="['<str>', '<str>', ...]"</code><br> <code>PANTS_PEX_CLI_KNOWN_VERSIONS</code><br>
</div> <div style="padding-left: 2em;"> <span style="color: green">default: <pre>[ "v2.1.108|macos_arm64|21d7803ef39203a6b2ae9f9e2678636e3c38ba17226ea33d6305f0683ab72e84|3848678", "v2.1.108|macos_x86_64|21d7803ef39203a6b2ae9f9e2678636e3c38ba17226ea33d6305f0683ab72e84|3848678", "v2.1.108|linux_x86_64|21d7803ef39203a6b2ae9f9e2678636e3c38ba17226ea33d6305f0683ab72e84|3848678", "v2.1.108|linux_arm64|21d7803ef39203a6b2ae9f9e2678636e3c38ba17226ea33d6305f0683ab72e84|3848678" ]</pre></span>
<br>
Known versions to verify downloads against.
Each element is a pipe-separated string of `version|platform|sha256|length`, where:
E.g., `3.1.2|macos_x86_64|6d0f18cd84b918c7b3edd0203e75569e0c7caecb1367bbbe409b44e28514f5be|42813`.
Values are space-stripped, so pipes can be indented for readability if necessary.
</div> <br>
<div style="color: purple">
### `use_unsupported_version`
<code>--pex-cli-use-unsupported-version=<UnsupportedVersionUsage></code><br> <code>PANTS_PEX_CLI_USE_UNSUPPORTED_VERSION</code><br>
</div> <div style="padding-left: 2em;"> <span style="color: green">one of: <code>error, warning</code></span><br> <span style="color: green">default: <code>error</code></span>
<br>
What action to take in case the requested version of pex is not supported.
Supported pex versions: >=2.1.108,<3.0
</div> <br>
<div style="color: purple">
### `url_template`
<code>--pex-cli-url-template=<str></code><br> <code>PANTS_PEX_CLI_URL_TEMPLATE</code><br>
</div> <div style="padding-left: 2em;"> <span style="color: green">default: <code>https://github.com/pantsbuild/pex/releases/download/{version}/pex</code></span>
<br>
URL to download the tool, either as a single binary file or a compressed file (e.g. zip file). You can change this to point to your own hosted file, e.g. to work with proxies or for access via the filesystem through a `file:$abspath` URL (e.g. `file:/this/is/absolute`, possibly by [templating the buildroot in a config file](🔗)).
Use `{version}` to have the value from --version substituted, and `{platform}` to have a value from --url-platform-mapping substituted in, depending on the current platform. For example, https://github.com/.../protoc-{version}-{platform}.zip.
</div> <br>
<div style="color: purple">
### `url_platform_mapping`
<code>--pex-cli-url-platform-mapping="{'key1': val1, 'key2': val2, ...}"</code><br> <code>PANTS_PEX_CLI_URL_PLATFORM_MAPPING</code><br>
</div> <div style="padding-left: 2em;"> <span style="color: green">default: <code>{}</code></span>
<br>
A dictionary mapping platforms to strings to be used when generating the URL to download the tool.
In --url-template, anytime the `{platform}` string is used, Pants will determine the current platform, and substitute `{platform}` with the respective value from your dictionary.
For example, if you define `{"macos_x86_64": "apple-darwin", "linux_x86_64": "unknown-linux"}`, and run Pants on Linux with an intel architecture, then `{platform}` will be substituted in the --url-template option with unknown-linux.
</div> <br>
## Deprecated options
None