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.
PEEP to add the option to save exact libraries versions to Pipfile
Thank you for contributing to Pipenv!
The issue
As described in #3441, it would be interesting if when installing a certain package with pipenv without specifying the version (
pipenv install scipy
, for example), there was a flag that saved the exact version that was installed to the Pipfile. Something like the--save-exact
flag in npm.The fix
Right now this can be accomplished, AFAIK, manually editing the version numbers in Pipfile, but it's quite annoying.
The checklist
news/
directory to describe this fix with the extension.bugfix
,.feature
,.behavior
,.doc
..vendor
. or.trivial
(this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.