vscode jupyter not seeing micromamba environments

[vttrifonov]

Recently our company switched from using conda to using micromamba for managing python environments. As a result my named environments get created under ~/.micromamba/envs and not ~/.conda/envs any more. This has made switching environments in vscode a real pain. Before (with conda and ~/.conda/envs) I can see all environments and just pick the one I need from the change kernel box in the jupyter notebook. Now the environments are not listed, so I need to get a terminal, activate the environment by hand, get the python path, select it as an interpreter, and then the environment appears in the change kernels box. But then vscode "forgets" the environment I have chosen so carefully, so I have to do the "select python interpreter" dance again. And again. And again...

How can I make vscode "just see" the environments in my ~/.micromamba/envs folder like it used to before switching to micromamba?

[DonJayamanne]

Thank you for filing this issue,
Does the micromamba environment show up in the list of Python environments when you use the command Python: Select Interpreter

[vttrifonov]

thanks for the quick response! no it does not. this is the other kink: i have to click on enter path and paste the path that i have copied from command-line...

[DonJayamanne]

Closing in favour of microsoft/python-environment-tools#25