Add an initial guide to virtual environments with micromamba #18
Conversation
alisterburt
changed the title
| @@ -45,6 +45,7 @@ nav: | |||
| - tutorial/github/github_pages.md | |||
| - Guides: | |||
| - guides/index.md | |||
| - Virtual Environments: guides/environments.md | |||
There was a problem hiding this comment.
Put at the top because it's early in the journey - is there a logical structure you're aiming at?
There was a problem hiding this comment.
nope not yet... just stuff I don't want to forget about
alisterburt
force-pushed
the
environments
branch
from
6e28722
to
4179b5a
Compare
There was a problem hiding this comment.
do you actually use micromamba as your daily driver?
I have tried it on a number of systems, and have found enough edge cases that I still tend to go for mambaforge these days...
I want to be able to use it all the time, but feel like it hasn't been stable enough
|
I've been using it for a couple of months now without any big issues... curious to hear what you've run into?! Windows installation does look a pain which is also a vote for mambaforge - the big thing for me is the lack of base env |
yep, totally agree. that would be a huge win for people not messing up their stuff. I honestly can't remember what the issues were! I just remember trying it on more than one occasion... feeling like everything was going great, and then running into some sort of hiccup that made me uninstall I guess it's time to do it again :) |
|
The CLI definitely isn't at parity with |
|
here's a minor issue, that hints at more general issues of "support" across various tooling platforms: at least without me doing something extra, VSCode is unable to determine the names of my micromamba environments: 
while it does fine for mambaforge: 
|
|
related issue here: (and I see our friend @psobolewskiPhD over there too 😂) |
|
I took the micromamba plunge, but haven't set up with VSCode yet. Edit: to note make this totally off-topic: Also one of the nicest mamba/micromamba things that I don't think vanilla conda does is: I use Not sure it's in the scope of the guide though, maybe as a tip at the end? with a link to the docs? |
|
|
||
| </div> | ||
|
|
||
| Next, setup `micromamba` to download packages from |
There was a problem hiding this comment.
| Next, setup `micromamba` to download packages from | |
| Next, setup `micromamba` to download packages exclusively from |
maybe worth the emphasis?
| ```console | ||
| $ (my-env) ➜ conda install numpy | ||
| ``` | ||
|
|
There was a problem hiding this comment.
| Note: you can append `--dry-run` to get a preview of what would be installed. |
Not sure this is placed correctly or won't ruin formatting...
|
I've have both conda and mamba aliased to micromamba, still no. I wouldn't be surprised if they are making assumptions beyond simply running a cli command |
|
okay - I've come around on this, micromamba is not to be recommended - too many issues with surrounding tools. to mambaforge! |
|
it's ok, time to move to pixi anyway! |
|
Oh man 🤦♂️
Too bad was rejected then https://peps.python.org/pep-0582/ PDM does support the concept though |
|
found another case where micromamba didn't work: when running benchmarks with asv, it looks for conda to make environments... and even though I had conda aliased to micromamba, it was still unable to build an env: …/dev/self/psygnal via 🅒 psygnal took 2.3s …
❯ make benchmark-compare
asv run --interleave-processes --skip-existing main^!
· Creating environments
·· Failure creating environment for conda-py3.10-HATCH_BUILD_HOOKS_ENABLE1
·· Could not find 'conda' in PATH
make: *** [benchmark-compare] Error 1
…/dev/self/psygnal on reduce-compare [$] via 🅒 psygnal
❯ which conda
conda: aliased to micromamba |
No description provided.