Fix incorrect command reminder after installs #6199
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
When installing new packages using
pipenv install <package>
the following reminder may be returned when thePipfile
is out of date:However, no such command
pipfile lock
exists. The next returned line proceeds to run the correct command for the user:So it appears the author actually meant the reminder message to read
pipenv lock
since that is what is subsequently run.Fix
Updated line of
pipenv/routines/install.py
to return correct command. See here