#2344 Support syncing input requirements to a lock file more easily. Issue created by jsirois With #2335, the correct set of arguments to

pex3 lock update

can be crafted to minimally update to a lock to an evolved set of input requirements. As noted here #2334 (comment) though, a nicer interface would be:

pex3 lock sync "req1<2" -r reqs.txt --constraints constraints.txt --lock lock.json -- pytest ...

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. pantsbuild/pex