Issue Type: Bug I'm sometimes (seems random) unable to select my python kernel. The Select Kernel options shows an empty list and I don't see any of my anaconda environments there. I also tried setting the interpreter by providing the co...
I opened an ipynb file and chose a specific kernel in which to run. I knew that there were packages I needed to install into that environment, so I launched a Python terminal erroneously thinking it would be the same environment used for my kernel. I unknowingly installed the needed package...
Can no longer select jupyter kernel in virtual environments created outside of /usr directory. In previous version other jupyter kernels would appear in list after restarting VSCode. (Seems to have stopped working with version 1.6, but not certain.) Now the only way to get Notebook to work w...
However, top right of interactive window will show UI for selecting different kernel on remote notebook server. Export .py file to .ipynb and open in new window. Notice that command palette for notebook context does have Jupyter: Select a Kernel as an available command. 👍 1 mparq ...
Create a new notebook file, "testnb.ipynb" - add and run a cell, make sure the my_venv Kernel actually starts. Exit code and fully delete my_env. Restart code and you can apparently never work with that notebook again - it indicates "No Kernel" in the top right but this cannot be...
Vscode reloads, I open a .ipynb file and vscode fails to connect at all. It's looking for some old kernel it can't find. I assume because there's some cache somewhere. Please note that when the logs mention localhost:9999 that port is bound via ssh tunnel to remoteserver:8888 where...