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
I recently upgraded to Micromamba 2.0.1 from 1.5.8, and I was not able to launch certain commands from powershell (like notepad or code). Looking a bit into it, I found that Micromamba 2.0.1, after activation, does not seem to honor system's PATH - instead of appending to the existing PATH from OS's environment variables, it overwrites it for the shell, i.e. the effects persist even after deactivation.
Take a look at the shell outputs for both the versions of micromamba.
I recently upgraded to Micromamba 2.0.1 from 1.5.8, and I was not able to launch certain commands from powershell (like notepad or code). Looking a bit into it, I found that Micromamba 2.0.1, after activation, does not seem to honor system's PATH - instead of appending to the existing PATH from OS's environment variables, it overwrites it for the shell, i.e. the effects persist even after deactivation.
Take a look at the shell outputs for both the versions of micromamba.
Update: This issue is already raised in mamba-org/mamba#3405
The text was updated successfully, but these errors were encountered: