Hello everyone! I'm Cody and I work at Parse.ly. We have an existing monorepo structure that contains a number of existing projects with some dependencies between some. I heard of pants from the "WTF is PEX" youtube talk, we've been experimenting what using pex based deploys might like but I'm very interested in integrating pants to make the whole process easier to manage. Super stoked to see there is a whole community for this tool.

Cool! Pex has had a lot of improvements since that video 7 years ago, including: • vendoring pip for the resolver, meaning it should build whatever pip can build • getting rid of overhead when running a Pex when using

--venv

, and less overhead with

--unzip

• byte-for-byte reproducibility

Oooh thank you for that share. From what I've been reading lately I'm kinda surprised that PEX isn't used more frequently. It solves a lot of issues.

It's just starting to get on folks' radar in a big way. Such as this lovely endorsement recently: https://twitter.com/ErbStephan/status/1451475076545761294?s=20

Hi! I am new to Pex as well (and intrigued). In the "WTF is PEX" youtube talk, Brian Wickman references a longer video closer to one hour long. Does anyone have a link to that?