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
I noticed there is a difference in behavior between running all cells in a notebook in Jupyter Lab/Notebook and VS Code: when an exception is raised in Jupyter Lab/Notebook, subsequent cells do not run. In VS Code, all cells run regardless of whether any exceptions were raised.
I am sure the former is the correct behavior so can this be considered a bug in the VS Code Python extension? I also see that VS Code itself is adding native notebook support so perhaps this will be addressed in that but I wanted to be sure this issue was recorded somewhere.
I've also verified the same behavior in the latest VS Code Insiders (1.47.0).
Thanks!
The text was updated successfully, but these errors were encountered:
@logan-pugh thanks for filing this. I took a look and confirm the same thing that you are seeing. We will discuss this internally, but we probably want to match the way Jupyter behaves here.
Thanks for your feedback. This issue will be addressed once VS Code adds native support for editing notebooks. Please see microsoft/vscode#91987. You can experiment by using VS Code insiders, which defaults to the new notebook experience.
I noticed there is a difference in behavior between running all cells in a notebook in Jupyter Lab/Notebook and VS Code: when an exception is raised in Jupyter Lab/Notebook, subsequent cells do not run. In VS Code, all cells run regardless of whether any exceptions were raised.
I am sure the former is the correct behavior so can this be considered a bug in the VS Code Python extension? I also see that VS Code itself is adding native notebook support so perhaps this will be addressed in that but I wanted to be sure this issue was recorded somewhere.
I've also verified the same behavior in the latest VS Code Insiders (1.47.0).
Thanks!
The text was updated successfully, but these errors were encountered: