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
meganrogge
changed the title
ipykernel 6 required for debugging to work
ipykernel 6 required for debugging to work - not informed when using lower version
Jun 29, 2021
meganrogge
changed the title
ipykernel 6 required for debugging to work - not informed when using lower version
ipykernel 6 required for debugging to work - not informed when using lower version and strange behavior
Jun 29, 2021
DavidKutu
changed the title
ipykernel 6 required for debugging to work - not informed when using lower version and strange behavior
[Endgame testing] ipykernel 6 required for debugging to work - not informed when using lower version and strange behavior
Jun 30, 2021
Now that ipykernel 6 just released. I was thinking we could always expose the button and have it show a message if you don't have it and offer a button to do the installation for you.
@roblourens had another idea to make this feel more native, to remove the button altogether and have the session start silently when you open the notebook, there would be no extra steps to start debugging, just set a breakpoint and run cells.
testing microsoft/vscode#127362 , debugged with @DavidKutu
Expected behaviour
I expected debugging to work with ipykernel 5.5.5 installed
Actual behaviour
It did not and had some confusing behavior:
Jupyter: Debug
appeared in the command palette, but only on window reloadTo resolve this, I had to uninstall ipykernel and re-install the latest version with
pip install ipykernel --pre
The text was updated successfully, but these errors were encountered: