How Pants uses Pex to run Python subprocesses.
Config section: <span style="color: purple"><code>[pex]</code></span>
## Basic options
None
## Advanced options
<div style="color: purple"> <h3><code>executable_search_paths</code></h3> <code>--pex-executable-search-paths="[<binary-paths>, <binary-paths>, ...]"</code><br> <code>PANTS_PEX_EXECUTABLE_SEARCH_PATHS</code><br> </div> <div style="padding-left: 2em;"> <span style="color: green">default: <pre>[ "<PATH>" ]</pre></span>
<br>
The PATH value that will be used by the PEX subprocess and any subprocesses it spawns.
The special string "<PATH>" will expand to the contents of the PATH env var.
</div> <br>
<div style="color: purple"> <h3><code>bootstrap_interpreter_names</code></h3> <code>--pex-bootstrap-interpreter-names="[<bootstrap-python-names>, <bootstrap-python-names>, ...]"</code><br> <code>PANTS_PEX_BOOTSTRAP_INTERPRETER_NAMES</code><br> </div> <div style="padding-left: 2em;"> <span style="color: green">default: <pre>[ "python", "python3", "python2" ]</pre></span>
<br>
The names of Python binaries to search for to bootstrap PEX files with.
This does not impact which Python interpreter is used to run your code, only what is used to run the PEX tool. See the `interpreter_search_paths` option in `[python]` to influence where interpreters are searched for.
</div> <br>
<div style="color: purple"> <h3><code>verbosity</code></h3> <code>--pex-verbosity=<int></code><br> <code>PANTS_PEX_VERBOSITY</code><br> </div> <div style="padding-left: 2em;"> <span style="color: green">default: <code>0</code></span>
<br>
Set the verbosity level of PEX logging, from 0 (no logging) up to 9 (max logging).
</div> <br>
## Deprecated options
None