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
In VS Code I've created a new notebook, don't save it and select my new virtual environment .venv
My understanding is that VS Code uses ipykernel in the virtual environment to power the notebook experience. My understanding is that it does not use any python packages outside my virtual environment.
When I run the code it looks like
I believe it also sometimes did look like that with Panel 1.3.8. I've just not reported it because trying again use to solve my problems.
It works when I try again
I create a new notebook and save it as Demo.ipynb. This time it works when I run
vs-code-works.mp4
The interactive environment works for me too.
Now an unsaved notebook works for me too.
The text was updated successfully, but these errors were encountered:
MarcSkovMadsen
changed the title
Panel not working in VS Code notebooks with non-saved Notebook
Panel not working in VS Code notebooks initially
Apr 2, 2024
I've created a new virtual environment with
panel==1.4.0
bokeh==3.4.0
ipywidgets==8.1.2
jupyter-bokeh==4.0.1
jupyterlab-widgets==3.0.10
widgetsnbextension==4.0.10
ipykernel==6.29.4
In VS Code I've created a new notebook, don't save it and select my new virtual environment .venv
My understanding is that VS Code uses ipykernel in the virtual environment to power the notebook experience. My understanding is that it does not use any python packages outside my virtual environment.
When I run the code it looks like
I believe it also sometimes did look like that with Panel 1.3.8. I've just not reported it because trying again use to solve my problems.
It works when I try again
I create a new notebook and save it as Demo.ipynb. This time it works when I run
vs-code-works.mp4
The interactive environment works for me too.
Now an unsaved notebook works for me too.
The text was updated successfully, but these errors were encountered: