How hard would it be to support merging a pex file...
# pexh
happy-kitchen-89482
03/26/2020, 1:26 AMHow hard would it be to support merging a pex file containing only requirements with one containing no requirements? This is an important special case, for example when running
./pants binarye
enough-analyst-54434
03/26/2020, 2:04 AMOne thing to think about as well is why make a requirements only PEX in the 1st place, why not just run a resolve and store the resulting ResolvedDistributions. Then you can build a binary straight up in 1 go with a PEXBuilder.
👍 1
enough-analyst-54434
03/26/2020, 2:04 AMIf its because your using a CLI and not the API, perhaps write a small cli that uses the resolver API.
enough-analyst-54434
03/26/2020, 4:08 AMThis is seeming like a better and better idea. So, a rule that uses the downloaded pex binary to generate a pex from a python file (a resource target in the Pants repo) that supports a small CLI that runs the resolver and plops out its solution in pinned requirements and wheel chroots to the EPR chroot for collection as output digests.
🚢 1
a
aloof-angle-91616
03/26/2020, 4:11 AMpotentially relevant work might be this draft PR that adds a few utilities to make it easier to use checked-in bash scripts in EPRs: https://github.com/pantsbuild/pants/pull/9101
aloof-angle-91616
03/26/2020, 4:14 AMre: the PR i just linked: i'm not sure i understand the need for the separate
create_bash_script_execution_request()aloof-angle-91616
03/26/2020, 4:16 AMa rule that unzips a file from a pex is something i've wanted for ipex in v2 as well (it currently just runs
unzip