Hey @enough-analyst-54434 following the Exec format error fixes for pex in 2.1.95 (thanks again), I’m seeing similar ENOEXEC errors in our build sandbox because the Pip instance called by the resolver invokes the pex venv main script directly. Would you be open to a change to the pip.tool.spawn_download_distributions call to invoke pip.pex via the

<venv_dir>/bin/python

?

I'm not following, can you explain what you're doing a bit more in detail?

building a pex under some long sandbox path: Calling resolver.resolve leads to exec format errors from pip.pex venv

Ah, gotcha. SGTM!

cool! I’ll put up a patch

If you get it up quick I can get it out in 2.1.96: https://github.com/pantsbuild/pex/pull/1838 If not I'll fork off another tiny release just after.

🕔

@early-needle-54791 unless you've made progress, I'd like to bang this out. I'll be going offline for ~10 days starting tomorrow and I'd like to ensure this case is sorted: https://github.com/pantsbuild/pex/issues/1842

Oh alright.

Sorry about that @early-needle-54791, I'd certainly welcome any contribution you have. I'm part-time and ~the only active Pex maintainer currently so things were cramped this time around. I'm also guessing you weren't aware of the PEP 517 / 518 case and the

str

type for venv pexes would not have helped you find that case 😕 Pex 2.1.97 release prep: https://github.com/pantsbuild/pex/pull/1844

Yeah exactly I didn’t know about the edge cases anyway so we would have had to have some back and forth.

You're welcome. Pex 2.1.97 is now released with this fix.

🎉