Skip to main content
Version: 2.2 (deprecated)

pex

How Pants uses Pex to run Python subprocesses.

Backend: ``

Config section: [pex]

Basic options​

None

Advanced options​

bootstrap_interpreter_names​

--pex-bootstrap-interpreter-names="[<bootstrap-python-names>, <bootstrap-python-names>, ...]"
PANTS_PEX_BOOTSTRAP_INTERPRETER_NAMES
pants.toml
[pex]
bootstrap_interpreter_names = [
    <bootstrap-python-names>,
    <bootstrap-python-names>,
    ...,
]
default: 
[
  "python",
  "python3",
  "python2"
]

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-setup] to influence where interpreters are searched for.

executable_search_paths​

--pex-executable-search-paths="[<binary-paths>, <binary-paths>, ...]"
PANTS_PEX_EXECUTABLE_SEARCH_PATHS
pants.toml
[pex]
executable_search_paths = [
    <binary-paths>,
    <binary-paths>,
    ...,
]
default: 
[
  "<PATH>"
]

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.

verbosity​

--pex-verbosity=<int>
PANTS_PEX_VERBOSITY
pants.toml
[pex]
verbosity = <int>
default: 0

Set the verbosity level of PEX logging, from 0 (no logging) up to 9 (max logging).

Deprecated options​

None

None