Skip to content

vscode jupyter not seeing micromamba environments #24812

Closed

Description

@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?

Activity

  1. added
    bugIssue identified by VS Code Team member as probable bug
    on Feb 12, 2025
  2. DonJayamanne commented on Feb 12, 2025

    @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

  3. vttrifonov commented on Feb 12, 2025

    @vttrifonov
    Author

    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...

  4. DonJayamanne commented on Feb 13, 2025

    @DonJayamanne
  5. added
    *duplicateIssue identified as a duplicate of another issue(s)
    and removed
    triage-neededNeeds assignment to the proper sub-team
    on Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    *duplicateIssue identified as a duplicate of another issue(s)bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from poster

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions