billowy-kite-9901
05/31/2022, 11:41 AM/usr/bin/env python
is called from the makefile.
Is there a way to give the same PEX environment ("installed" packages) to python scripts called this way? 🤔enough-analyst-54434
05/31/2022, 11:51 AMexecution_mode="venv"
on the relevant pex_binary
target(s)?: https://www.pantsbuild.org/docs/reference-pex_binary#codeexecution_modecodeenough-analyst-54434
05/31/2022, 11:52 AMbin/
dir to the PATH
.billowy-kite-9901
05/31/2022, 11:57 AM--venv
to the pex
tool and running the resulting file with PEX_VENV=1 ./my-pex-file.pex
, but python
still resolves to /usr/bin/python
enough-analyst-54434
05/31/2022, 12:01 PM--venv prepend
if manually using Pex (Pants does this for you).enough-analyst-54434
05/31/2022, 12:02 PMPEX_VENV=1
when running that PEX, --venv ...
bakes the execution mode into the PEX's metadata.billowy-kite-9901
05/31/2022, 12:04 PMbillowy-kite-9901
05/31/2022, 12:04 PM--venv
option on the readthedocs site:
https://pex.readthedocs.io/en/latest/buildingpex.htmlbillowy-kite-9901
05/31/2022, 12:06 PMenough-analyst-54434
05/31/2022, 12:07 PMpex --help
says more.enough-analyst-54434
05/31/2022, 12:10 PMpex --help
and pex --help-variables
are your best bets.enough-analyst-54434
05/31/2022, 12:11 PM--sh-boot
.