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.
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
Fix display of env activation message and co #3715
Fix display of env activation message and co #3715
Changes from 2 commits
1506023
b9e875c
19ce847
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Currently the message is shown for installations and updates if the target prefix is different than the currently activated one. Should we preserve this behavior?
Also, should the message rather be printer after the call to
install_for_other_pkgmgr
(namely just before theelse
)?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.
Indeed, and I was going to keep it that way but I realized
conda
was only showing activation message with environment creation, and that actually makes more sense and is less verbose (recommending env activation sounds relevant when the user creates a new environment but seems redundant when installing/updating).For now, I suggest to do it this way, and if we want to restore the previous behavior, that should be straightforward by adding
print_activation_message
where needed.Good question! I put it right after the transaction execution to preserve the order of printing messages (since it was inside
Transaction::execute()
). But that could be discussed: either consider that the transaction is finished and print the activation message, and then handlepip
packages (or anything else?) considering we do not recommend it (cf. warning that we added recently) or print the activation message after everything is done including things we don't really approve.Note however that
install_for_other_pkgmgr
does not involveTransaction
so it's supposed to be done with before handling other pkg managers.In my opinion, let's keep it as it is.
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.
Same suggestions as above.
Side-note: are there a way we could factor (parts of)
install_explicit_with_transaction
andinstall_specs_impl
in another PR?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.
Depends on what we want to refactor and if we need some parts in the codebase reworked first. But we can look into it.