John Sirois

@danxmoran this amounts to a feature request against Pex. Today Pex supports: 1. `pex3 lock update my.lock` to update a whole lockfile with latest that meet the original requirement constraints....

I missed the bit about the check. FWIW, this exists today over in Pex: Prep a lock: ``` $ pex3 lock create requests -o lock ``` Update it right away;...

I guess adding an optional 'check' argument to `--dry-run`; i.e: `--dry-run check` which ran a `--dry-run` but exited non-zero if there are updates might make sense.

The `pex3 lock update --dry-run check` implementation is here: https://github.com/pantsbuild/pex/pull/1799

As has Pex, since 2022. Pants has been exceedingly slow to adopt the Pex support. There was a recent engagement that produced fixes and more features from Pex for all...

Is `mypackage` figurative or real? If it truly is your own package, are the multiple representatives on different indexes supposed to be identical (and just the wheel build process is...

> Snapshot index is for development - we may publish snapshot which is mutable and use this snapshot in another projects. I want to focus here. This is _not_ OK....

Ok, thanks for the confirmation. I still would like to leave this issue open to investigate the indexes / hashes mismatch. There may be something better Pex could be doing.

@MajerMartin one missing piece of information here is what `--pip-version` Pants is passing Pex, if any (as well as the Pex version being used). Pip has changed how it handles...

One other note - I referenced using local version identifiers when creating snapshots, but that's just one of several schemes you could use. Since these are pre-releases, you could also...