John Sirois

@tgolsson if you have the time, it would be super useful to get: 1. The exact command line to generate the lock. 2. The exact command line to exercise the...

Thanks @tgolsson , I'll check this out tomorrow. As to the pip-2020-resolver, that's the default and only supported option for any Pip version in at least the last 2 years;...

Ok, thanks for the command line @tgolsson - that was gold: ```console # Run pex3 lock create in verbose mode: :; pex3 lock create --pip-log pip.log --pip-version latest-compatible --resolver pip-2020-resolver...

Ok, PEP-691 confusion was not it. I needed to change a data structure to admit for the possibility the same wheel filename may appear multiple times (and have different contents)....

Ok, this corner here is pretty narrow. If the extra indexes are --find-links (local or remote), or the index is a traditional [PEP-503](https://peps.python.org/pep-0503/) simple index - there are no problems....

Alrighty, that was way too long, but the hash issue should now be fixed in https://github.com/pex-tool/pex/releases/tag/v2.54.2. Thanks again for the public repro case @tgolsson .

The bespoke Pex resolver that had this issue has since been replaced by Pip and no longer exhibits this problem.

One place you could look for now is Pex, it supports these use cases directly with almost 100% of the hard work done by Pip. For the OP from @ion-elgreco,...

Why does the existing export-subset, fed back in to `pex -r ...` not suffice? The resulting requirements file has hashes, and the underlying `pip download` call checks these; so is...

A side note: you often reference commands like `PEX_SCRIPT=pex3 pex ...`. This is extremely non-idiomatic / Pants specific. In almost all cases `pex` will be the `pex` console script, for...