You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
Many user would want conda's auto_activate_base: false configuration set, because having the base environment always activated when starting a new shell means having to deal with environment conflicts when dealing with apt, brew and other packages that use python in the background.
Not having this setting set to true makes Topgrade skip conda when upgrading.
Is there a way we can make topgrade updgrade conda without having the base environment activated.
In my own case, the conda executable is visible, the base env just isn't activate.
Something like conda update -n base --all -y
The text was updated successfully, but these errors were encountered:
Many user would want conda's
auto_activate_base: false
configuration set, because having the base environment always activated when starting a new shell means having to deal with environment conflicts when dealing with apt, brew and other packages that use python in the background.Not having this setting set to true makes Topgrade skip conda when upgrading.
Is there a way we can make topgrade updgrade conda without having the base environment activated.
In my own case, the
conda
executable is visible, the base env just isn't activate.Something like
conda update -n base --all -y
The text was updated successfully, but these errors were encountered: