#2334 pex lock update: mechanism to change the version specifier if an existing requirement (or constraint?) Issue created by cburroughs With

--project=

one can adjust the current version of a project anywhere within the existing version specifier, but not change the specifier without regenerating the entire lockfile. This would be useful for the same reasons as adding a new project with the lock is. I'm unsure if constraints need separate consideration for changing the version specifier. That is pip let's you mange them separately:

$ cat c.txt 
ansicolors<1.1.7
$ pip install -c c.txt  ansicolors==1.0.2

But I'm not sure if that means they must map to separate cli flags in Pex. pantsbuild/pex