migrating from miniconda or anaconda to mambaforge #435
Unanswered
JessicaS11
asked this question in
Q&A
Replies: 4 comments 4 replies
-
|
The underlying problem is that the transition from "anaconda's channels" to "conda-forge's channel" is REALLY painful. Fundamentally, trying to "update base" from using anaconda channels to conda-forge is almost surely "going to fail if you have anything other than conda installed in base". In my experience, with the vanilla command: mostly fails. This "uninstallation" is really hard to articulate. Basically, Mambaforge installs mamba in the base environment, but all the packages start "from conda-forge" so there is "update" path. What does |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks for the fast reply, @hmaarrfk!
That makes sense. Perhaps this accidentally worked for me years ago because I use conda-forge's channel instead of anaconda's.
"The base environment" for the new mambaforge install, not my pre-existing anaconda install? So I could follow the procedure to uninstall anaconda without messing up my new mambaforge?
|
Beta Was this translation helpful? Give feedback.
-
|
Typically "uninstalling" anaconda means just removing everything under the anaconda directory. That willremove all your environments.... not fun unless you took meticulous notes. Can you "reactivate" your anaconda install and provide the same output for |
Beta Was this translation helpful? Give feedback.
1 reply
-
Totally! I was thinking more for the future when I've recreated or removed the environments I need. With previous anaconda install
|
Beta Was this translation helpful? Give feedback.
-
|
if years back, you installed and have already installed I have some old environments that are still installed in It is the transition from anaconda -> conda-forge that can be painful in 2023. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
At this point, I have no idea what I did back then, just that it worked and I've been happily using mamba within it for the last few years. : ) I can see why this is not the recommended approach now though. I saw in the docs that given it's newness, micromamba is still experimental and primarily used in CI pipelines (hence why I went with the mambaforge install). Should I encourage new users to install mambaforge if they want to try mamba out? |
Beta Was this translation helpful? Give feedback.
-
|
For 1, you can use |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thank you - somehow missed that config value! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been using mamba installed in my base environment for a few years (and tell everyone about it because it is so fast!) and recently noted that this method is not recommended. As a result, I'm wondering a few things:
Thanks for your insights!
EDITS: edited to add links to the replies addressing each question, since GitHub won't let me select more than one post as the "answer".
Beta Was this translation helpful? Give feedback.
All reactions