The idea is to perform a minimal lock update given the input requirements and constraints (or noop if reqs have not changed) and, if -- is present, execute the command line following it after syncing that command's venv with the lock.
This new notion of an ~auto minimal lock update would parse all input requirements and use the new features from #2335 to form the appropriate set of -R replacements and -d deletes to bring the lock in sync.
With #2335, the correct set of arguments to
pex3 lock updatecan be crafted to minimally update to a lock to an evolved set of input requirements. As noted here https://github.com/pantsbuild/pex/issues/2334#issuecomment-1900963246 though, a nicer interface would be:The idea is to perform a minimal lock update given the input requirements and constraints (or noop if reqs have not changed) and, if
--is present, execute the command line following it after syncing that command's venv with the lock.This new notion of an ~auto minimal lock update would parse all input requirements and use the new features from #2335 to form the appropriate set of
-Rreplacements and-ddeletes to bring the lock in sync.