In the vein of https://github.com/pantsbuild/pex/issues/789 (discussing solutions to ship around pex files without all of their requirements stuffed inside) => I've created a doc discussing the alternative solutions we've come up with, which also splits up the problem of "dehydrated" pex files into:
1. How to create "dehydrated" pex files (without requirements)?
2. How to re-hydrate those requirements to run the pex (there are many solutions to this part)?
You should have comment access (https://docs.google.com/document/d/1B_g0Ofs8aQsJtrePPR1PCtSAKgBG1o59AhS_NwfFnbI/edit?usp=sharing) -- please let me know if I can clarify the problem or the solutions. This comes from a workstream at Twitter where we're trying to reduce redeploy times for pex files by not shipping around >1GB files with all the 3rdparty requirements attached, mainly for large ML applications. I think this approach is somewhat novel, but I'd love to know if we're missing something obvious.