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
When attempting to update conda-smithy with mamba, it only considers conda-smithy itself for update and not all dependencies of conda-smithy, since the dependency specs are still valid.
The text was updated successfully, but these errors were encountered:
conda's habit of updating everything by default is a bit of a bugbear of mine so I always pass the --no-update-deps flag - applying the "if it ain't broken, don't fix it" policy.
I dislike updating everything (when it isn't strictly necessary) because it often dramatically slows down what should be a simple single package update and it interacts badly with conda's other habit of shuffling packages
If I want to update all my dependencies I do an explicit conda update --all
pip has introduced an upgrade strategy flag for this, with the default of "only-if-needed" and "eager" for opting in to updating all packages in the dependency tree. I think for folks choosing mamba, which should be folks looking for an optimized experience, defaulting to the smaller still-valid delta is a good choice. As long as there's still the option for eager transactions, I think it's okay or even good to do the smaller thing.
When attempting to update conda-smithy with mamba, it only considers conda-smithy itself for update and not all dependencies of conda-smithy, since the dependency specs are still valid.
The text was updated successfully, but these errors were encountered: