New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pipenv 3000 install (behavioral refactor) #6098
base: main
Are you sure you want to change the base?
Conversation
This PR looks good. What's still missing is an update to docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should definitely add documentation about this.
Huh, I'm a bit confused. I only see the logic for I know some people at my work sometimes edit the pipfile directly and then run |
Thanks for checking, I probably missed something in the refactor -- will revisit soon. |
The issue
It has been long requested that:
pipenv install
have the same behavior aspipenv sync
when no packages are requestedand
pipenv install package
has the behavior ofpipenv update
which means only
pipenv lock
will regenerate the whole lock.Fixes #5992
Fixes #6070
Fixes #6048
The checklist
news/
directory to describe this fix with the extension.bugfix.rst
,.feature.rst
,.behavior.rst
,.doc.rst
..vendor.rst
. or.trivial.rst
(this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.