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
First, I'd like to say that Mamba is an awesome initiative, I've tried mamba 0.0.7, and it worked very well with mamba install and mamba create, sometimes making the solver 15x faster, with no other apparent differences from the results of conda commands!
conda env update is an important feature, we depend on it to update our environments from environment.yml files, especially because of the --prune flag, that guarantees that the env is an exact match of the spec defined in environment.yml (removing extra packages). I've tried to use mamba env update, but it seems to have no effect in the performance this case (looks like it's using conda solver).
The text was updated successfully, but these errors were encountered:
indeed, we haven't put in the work to make mamba env update work and it's falling back to conda for this command (also the --prune flag has not yet been taken care of). It will be a little bit of work ... we need to figure out what arguments to pass to libsolv to make it happen :)
First, I'd like to say that Mamba is an awesome initiative, I've tried
mamba 0.0.7
, and it worked very well withmamba install
andmamba create
, sometimes making the solver 15x faster, with no other apparent differences from the results ofconda
commands!conda env update
is an important feature, we depend on it to update our environments fromenvironment.yml
files, especially because of the--prune
flag, that guarantees that the env is an exact match of the spec defined inenvironment.yml
(removing extra packages). I've tried to usemamba env update
, but it seems to have no effect in the performance this case (looks like it's usingconda
solver).The text was updated successfully, but these errors were encountered: