witty-crayon-22786
04/12/2019, 4:35 PM--inherit-sitepackages
?enough-analyst-54434
04/13/2019, 12:37 AM--inherit-path=(fallback|prefer)
when building the pex to get it to not scrub sys.path. You can observe scrubbing (or lack thereof) by running the pex with PEX_VERBOSE=9
. You can also sanity check the pex with unzip -qc <pex file> PEX-INFO | jq .inherit_path
. At runtime there is the PEX_INHERIT_PATH
env var / slurping that from .pexrc. Perhaps you are being bit by the last.witty-crayon-22786
04/13/2019, 12:41 AMwitty-crayon-22786
04/15/2019, 5:41 PMpex: Not a tainted path element: /Users/example/.venvburrito/lib/python2.7/site-packages
pex: Not a tainted path element: /Users/example/.venvburrito/lib/python2.7/site-packages/setuptools-28.8.0-py2.7.egg
pex: Not a tainted path element: /Users/example/.venvburrito/lib/python2.7/site-packages/pip-9.0.1-py2.7.egg
witty-crayon-22786
04/15/2019, 5:43 PMvenvburrito
entry caused a few users some issuesenough-analyst-54434
04/15/2019, 10:20 PMpex: Not a tainted path element: .../site-packages
implies PEX_INHERIT_PATH. That is the crucial investigatory bit to suss. If set in PEX-INFO, env or via .pexrc that is the issue and it's of the foisted on petard variety. If not, it's a pex sys.path
scrubbing bug.witty-crayon-22786
04/15/2019, 10:25 PM$ unzip -qc ~/.cache/pants/pex/bin/pants.pex/1.15.0rc0-git5c01b701/pants.pex PEX-INFO | jq .inherit_path
"false"
enough-analyst-54434
04/15/2019, 10:25 PMwitty-crayon-22786
04/15/2019, 10:25 PMPEX
-related env... i'll double check that we're not setting it anywherewitty-crayon-22786
04/15/2019, 10:26 PM~/.pexrc
sets PEX_PYTHON_PATH
and PEX_PYTHON
, but not inheritwitty-crayon-22786
04/15/2019, 10:26 PMPEX_INHERIT_PATH
witty-crayon-22786
04/15/2019, 10:27 PMenough-analyst-54434
04/15/2019, 10:27 PMwitty-crayon-22786
04/15/2019, 10:28 PMenough-analyst-54434
04/15/2019, 10:28 PMwitty-crayon-22786
04/15/2019, 10:48 PMenough-analyst-54434
04/15/2019, 10:51 PM