micromamba is an implementation detail, a clone of conda program, should be invisible detail I think, so I’m not sure why you’re getting the error. Maybe it shouldn’t happen?
As @Palli said, you must have it installed, so the simplest solution (workaround) is to provide the full file path to where ever micromamba is stored, which is going to be in ~/.julia somewhere. It looks like you’re on Linux, so maybe do a locate or find?
One thing I like to do with my conda envs is add an alias so I don’t have to type conda activate all the time. So you could do something similar when you find the binary. Just add some version of this to your .bashrc file
alias my_env='micromamba activate /path/to/micromamba'
OK, I did: locate micromamba and found the path.
I then created a link:
cd .local/bin
ln -s /home/ufechner/.julia/artifacts/87052ac9aec71548f804b30280151288cb1ed40e/bin/micromamba
Now I can run micromamba, and can activate my environment, but there are still issues when using ipython3 . Well I guess I need to read some more of the micromamba documentation.
You can get the path to micromamba with MicroMamba.executable(). Micromamba is totally self contained so you can copy/link this to somewhere in your PATH.
Though for interactive usage I’d probably recommend installing Mamba instead via the MiniForge distribution: GitHub - conda-forge/miniforge: A conda-forge distribution.. Conda/Mamba/MicroMamba environments are all the same so you can mix and match tools.
I can run now ipython and interactively debug Python scripts. In VSCode I activated the
interpreter .CondaPkg/env/bin/python, so syntax highlighting etc works also fine.