Improve package operations management #4336
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sdispater
added
area/cli
sdispater
force-pushed
the
improve-operations-transactions
branch
2 times, most recently
from
7176e5f to
6dce09c
Compare
sdispater
force-pushed
the
improve-operations-transactions
branch
from
6dce09c to
ea8fb8c
Compare
Merged
3 tasks
10 tasks
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
This PR aims at improving the user experience when installing packages and at minimizing the install/uninstall operations when ignoring groups or opting-in groups.
An example of this is the following sequence:
$ poetry install $ poetry install --without dev # formerly --no-devIt would remove the existing development packages which was counter-intuitive. Now, the existing development packages will be kept in the environment.
Any locked packages will be kept in the environment regardless of what is asked via the
installcommand unless the--syncoption is specified.Overall, this should be less surprising for end users makes working with dependency groups easier.
Pull Request Check List