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
Bug: Switching environments after a notebook has been opened does not switch the environment for the notebook.
Use case: I open vscode to edit an ipython notebook that relies on a certain environment. I try to execute the notebook, and then realize I am in the wrong environment. So I select the new environment. At this point, there doesn't appear to be any way to get that notebook to use the new environment without completely quitting VSCode
Steps to cause the bug to occur
Open an iPython notebook
Execute notebook
Switch conda environments with Interpreter picker
Execute notebook again
Notice it's still using old environment
Actual & Expected behavior
Actual Behavior: The notebook executes in the environment active when VSCode starts no matter what you do with switching interpreters
Expected Behavior: Switching environments should re-start notebook kernel in new environment.
Bug: Switching environments after a notebook has been opened does not switch the environment for the notebook.
Use case: I open vscode to edit an ipython notebook that relies on a certain environment. I try to execute the notebook, and then realize I am in the wrong environment. So I select the new environment. At this point, there doesn't appear to be any way to get that notebook to use the new environment without completely quitting VSCode
Steps to cause the bug to occur
Actual & Expected behavior
Actual Behavior: The notebook executes in the environment active when VSCode starts no matter what you do with switching interpreters
Expected Behavior: Switching environments should re-start notebook kernel in new environment.
Your Jupyter and/or Python environment
Please provide as much info as you readily know
Developer Tools Console Output
The text was updated successfully, but these errors were encountered: