John Sirois
Hey Henry! Yeah, I think 2 makes sense as a feature on its own. As to 1, I'm still hazy too. you could definitely merge source roots just using `-D...
@aviau, are you too a Pants user or a direct Pex user? As a direct Pex user you have easier access to debug logs (-v (up to 9 times) or...
Ok. As @cburroughs said here: > But on a pendantic note in pex land, I do still think "error downloading required artifacts" as a message should be reserved for actual...
@DLukeNelson that mostly makes sense. You're seeing things through Pants eyes though; so the `[pex] ` stuff is redundant from the Pex layer. With Pex verbose logging turned on Pex...
Ok, the better download error messages are now available in v2.13.0.
OK, re-read https://peps.python.org/pep-0440/#compatible-release and `~=3.10` does mean `>=3.10,==3.*` aka `>=3.10,
Circling back to the confusing error message in the Pip download logs of `Link requires a different Python (3.10.4 not in: '>=3.7,
I think 1 is fine to solve as you suggest. Pex has a suite of determinism tests, but they assume you're trying to build the PEX again at some other...
Hrm, ok. I'm not sure I like the umask munging angle. I need to think on that a bit. Catering to differing OS / filesystem makes sense - its prevalent....
@manuzhang it sounds like you accepted solving the disk full condition with a higher level wrapper. As such, I'll close this issue and the associated PR.