John Sirois

`PEX_INHERIT_PATH` behavior is non-obvious in general. The only really sane way to get what you mean is to say `PEX_INHERIT_PATH=... /this/python my.pex ...`. That style says inherit `/this/python`'s sys.path in...

Re-reading the original description, I find PEX_PYTHON works just fine: ``` /tmp/pex-issues-1344 $ python -mvenv example /tmp/pex-issues-1344 $ source example/bin/activate (example) /tmp/pex-issues-1344 $ pip -q install -U pip (example) /tmp/pex-issues-1344...

Ok. That's not really what I meant - I was just pointing out I did not repro your failure to get `PEX_PYTHON` working. In the docs I'll be proposing the...

@juyoung-yoo there is not enough information here to help debug.Is there any way you can provide an open-source example to reproduce the issue with? Also note that you need not...

There are 0 Mac specific wheels on PyPI for setproctitle 1.2.2: https://pypi.org/project/setproctitle/1.2.2/#files So, Pex must be building the sdist into a wheel (via `pip wheel`) and then later trying to...

@chrisjrn to confirm this is a Pex problem and not a Pants problem, does `pex --python /usr/local/Cellar/[email protected]/3.9.5/Frameworks/Python.framework/Versions/3.9/bin/python3.9 setproctitle==1.2.2` fail similarly?

I have no access to this hardware, even via CI; so I appreciate all the digging you can do to help debug this.

OK. I'm pretty sure this is an instance of #1020. Namely, the sequence is: *1. At build time, the IC picks out an arm64 arch Python and so an arm64...

This is techinically a dup, but I'll leave it open to circle back and get a test from you @chrisjrn or @Eric-Arellano once #1020 is fixed since the whole arm...

The transition away from a legacy setup.py build was definitely by design. I've never used pip editable mode so I probably can't provide great guidance. I know when debugging PEX...