Can't set existing venv as kernel #16117
Unanswered
jaymc-arg
asked this question in
Questions and Answers
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to set a venv in vsocode as always, but I do not see them any more listed between the venvs I'been using.
If I wanted to use an existing environment I entered the interpreter path and the venv appeared with it's name as an option. Now when I do select the specified python venv, a new
.venv
folder is created in the directory workspace with as if I wanted to create a new environment and it's set as active so I can never choose the env I want to.Jupyter extension v2024.9.1
VSCode v2024.9.1
Is this happening to anyone?
EDIT:
Found this workarround , but I think this is maybe an issue.
Beta Was this translation helpful? Give feedback.
All reactions