John Sirois

> Ah, if you think it works sufficiently well/captures everything it needs to, I'm happy to use that as official guidance. Yup, should work just fine and give all the...

@huonw if you find issues with the `export-subset` -> `pex -r ...` setup, let me know. The path you were pushing for here suffers from an impedance mismatch that you'd...

> Ah, sorry. I like the all-in-one pex a lot: I have plopped it into my $PATH and then use it to install random Python tools (unrelated to Pants). I...

> make the pex3 entrypoint able to do everything (e.g. add a new subcommand pex3 build $args that does the same thing as pex $args) Yup. That has been exactly...

Ah, yeah. That's right. I went through some hoops to support locks of both VCS requirements and local project directories, neither of which Pip's `--hash` supports. Ok then. My comment...

Ok, I assigned you to help me keep track not to touch this.

@huonw this appears to be going nowhere fast. I'll take over here in the next few days unless I hear otherwise from you. This is a reasonable feature regardless of...

This is now released in 2.31.0: https://github.com/pex-tool/pex/releases/tag/v2.31.0

Yes. Although, a quick scan of usages seems to suggest it shouldn't be a new form, all callers should have to deal with the exception.

With the switch from the the Pex bespoke resolver to Pip in 2.x and conversion of all disk cache reads and writes to using `atomic_directory`, this problem is both obsolete...