John Sirois

Still some issues to work through on that PR https://github.com/pex-tool/pex/pull/2409. I may not get back to this until the 29th or so.

@TonySherman can you provide more context for your case? Notably, it seems to involve Pants and, fwict maybe involves Pants performing a subset of a PEX repository? For example, creating...

@TonySherman actually a PEX repository subset works fine. Using the `exclude.pex` from above: ``` # ~ :; pex --pex-repository exclude.pex requests -o requests-subset.pex # ~ :; ./requests-subset.pex -c 'import requests;...

I'm going to let #2409 close this issue. I've broken out the `--provided` idea to #2426.

Alright. The now polished `--exclude` is available in 2.4.0: https://github.com/pex-tool/pex/releases/tag/v2.4.0

@astrojuanlu that's good to know, however not enough. `uv pip compile` just emits hashed version pins (with markers) - it does not also provide distribution metadata which Pex needs in...

Yes, but I think no one here has any clue what that actually means. I would love someone to step up and wrestle with how much special case code they...

> @jsirois Could you expand on what distribution metadata uv doesn't emit? Maybe we can ask them to emit that metadata. @kuza55 I think my point is "we" need to...

Let me sharpen this even more. IIUC there is not a desire to make Pex faster / better here, there is actually just a desire to get Pants performing better,...

@kuza55 I think the issue is both, but agreed the bigger issue is no one willing to step up. As I said above, I won't be getting to it any...