John Sirois

As an aside, having to use editable mode implies a tight API coupling. So far, PEX has generally assumed it's only close API consumer was Pants. I'd be interested to...

I think starting things off with 0 magic would be great. Simply supporting `pex3 cache purge` in a multi-process safe way would be great. That would be == to `rm...

@zmanji that seems to make sense, although there is a detail to iron out: what does cache add for an sdist mean? Naively this builds and installs the sdist in...

It turns out #1661 had to deal with 1 (versioning the `installed_wheels` portion of the cache and all the other portions that symlinked into it (`venvs` and `unzipped_pexes`)) and 2...

I broke out #1662 for item 2 since that looks closeable.

Yeah, saw that. It won't be useable for `--style universal` locks until they tackle multiplatform (or we contribute it) - which they call out as a TODO. Ditto `--platform` and...

Maybe by the time the uv rise to the one true tool comes to pass - which is insane - Your language's tool in another language becuase yours is too...

Lots of people reacting to this - I'm going to assume that means folks agree Python / Pip / Pex are too slow right now and there is demand for...

One thing that struck me is most folks are probably ignorant of pip `--use-{feature,deprecated}` which Pex has used to provide a toggle between the `--resolver-version pip-{legacy,2020}-resolver` for many years now....

Ok, the `--use-feature` can be passed via requirements file already and it turns out via a saga documented in #2375 that `fast-deps` is slower for now anyhow.