Would anyone be able to point me towards where pants actually invokes pex under the hood during the process of building a

pex_binary

? Trying to figure out the exact arguments that

pex

is called with as part of writing a Bazel

pex_binary

target (to ease our transition to pants)

The exact command gets generated from many settings you've configured. The easiest way is to run

./pants --no-proccess-cleanup package ...

It will log tempdirs used for processes, one of which will be for building the pex. Open the sandbox and inspect

__run.sh

for the command

Ah nice thank you @bitter-ability-32190! looks like its something like

/usr/local/bin/python ./pex --tmpdir .tmp --python-path $'...path entries...' --output-file my_binary.pex --no-emit-warnings --manylinux manylinux2014 --intransitive --interpreter-constraint $'CPython==3.9.13' $'--sources-directory=source_files' --no-pypi $'--index=<https://pypi.org/simple/>' --resolver-version pip-2020-resolver --layout zipapp

Found this in the tempdir that assembled

local_dist.pex

Hmmm local dist is usually something else. There should be a later tempdir