Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change in python version of enviroment not reflected in kernel selection #6126

Closed
grudloff opened this issue Jun 4, 2021 · 8 comments
Closed
Labels
bug Issue identified by VS Code Team member as probable bug notebook-kernel Kernels issues (start/restart/switch/execution, install ipykernel)

Comments

@grudloff
Copy link

grudloff commented Jun 4, 2021

Environment data

  • VS Code version: 1.57.0
  • Jupyter Extension version : v2021.6.902307158
  • Python Extension version : v2021.6.897246044-dev
  • OS and version: Windows_NT x64 10.0.19041
  • Python and Anaconda version: 3.8.10 and 4.10.1
  • Type of virtual environment used : conda
  • Jupyter server running: Local

If an environment is deleted, and a new one is created with the same name but the python version is different this information won't be updated on the kernel selection or the interpreter selection.

@grudloff grudloff added the bug Issue identified by VS Code Team member as probable bug label Jun 4, 2021
@claudiaregio
Copy link
Contributor

@grudloff How are you deleting your environment? Does this still occur after you reload VS Code?

@claudiaregio claudiaregio added the info-needed Issue requires more information from poster label Jun 4, 2021
@grudloff
Copy link
Author

grudloff commented Jun 5, 2021

I am deleting through the cli with conda env remove --name env-name. Yes, this persists after reopening VS Code.

@claudiaregio
Copy link
Contributor

@grudloff If you go into your file directory and follow the path to the interpreter, is it still there?

I created a test environment, confirmed I could use it and then removed it as you did. When I reloaded VS Code the option was still there. I followed the path below in my file directory and the env "test" was still there. I had to delete it and reload VS Code for the option to be removed.

image

@DonJayamanne
Copy link
Contributor

Duplicate of #6164

@DonJayamanne
Copy link
Contributor

Sorry, not a duplicate of #6164

@DonJayamanne DonJayamanne added notebook-kernel Kernels issues (start/restart/switch/execution, install ipykernel) and removed info-needed Issue requires more information from poster labels Jun 7, 2021
@DonJayamanne
Copy link
Contributor

I can repro this, we store the display name & the like in the kernel spec.
We need a way to update this information.

@grudloff
Copy link
Author

grudloff commented Jun 7, 2021

@grudloff If you go into your file directory and follow the path to the interpreter, is it still there?

I created a test environment, confirmed I could use it and then removed it as you did. When I reloaded VS Code the option was still there. I followed the path below in my file directory and the env "test" was still there. I had to delete it and reload VS Code for the option to be removed.

image

Yes! Conda doesn't delete the folder after the environment is removed.

@DonJayamanne
Copy link
Contributor

Closing this issue, as this shouldn't be an issue anymore.
We don't display the kernels anymore, we display the intepreters in favor of the kernels.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug notebook-kernel Kernels issues (start/restart/switch/execution, install ipykernel)
Projects
None yet
Development

No branches or pull requests

4 participants