pipenv clean [perhaps] should not update Pipfile.lock

On one hand, help for clean command suggests that the lock file will only be read:

> pipenv clean --help
Usage: pipenv clean [OPTIONS]

  Uninstalls all packages not specified in Pipfile.lock.

...

On the other, in my case, the log suggests that the lock file got updated:

> pipenv clean -v
Pipfile.lock (e3d06d) out of date, updating to (327524)…
Locking [dev-packages] dependencies…
✔ Success!
Using pip: -i https://pypi.org/simple --extra-index-url https://[private]/pypi/
Using pip: -i https://pypi.org/simple --extra-index-url https://[private]/pypi/
Using pip: -i https://pypi.org/simple --extra-index-url https://[private]/pypi/

                          ROUND 1
Current constraints:
...

Clearly I don’t quite understand the internal mechanics of pipenv. Overall this seems inconsistent.

TBH, it is quite possible that my lock file did not match the pip file, as I was messing out with some dependencies and could have forgotten to lock dep list. I’m not quite sure what would be the right thing for the command to do in this case.

[techalchemy]

There is an API discussion to have here but mostly locking happened because your Pipfile was out of sync with your lockfile. This is a side effect of some other parts of the code, honestly, and if you haven’t locked yet then the new packages obviously haven’t been installed. Clean probably shouldn’t require this— it should just use the current lockfile

[satshabad-cr]

I encountered this as well, and it’s non-intuitive