From 0a12393d09ff3d1ec05a78d001e281ff9acf7dc0 Mon Sep 17 00:00:00 2001 From: Eliah Kagan Date: Sun, 3 Dec 2023 17:32:49 -0600 Subject: [PATCH] Tweak wording in using-notebooks Adding raises-exception support may be out of scope for vscode-jupyter due to lack of widespread interest in the feature. This slightly rewords the second on VS Code to avoid falsely implying that the project has committed to adding raises-exception support or that it will necessarily be added. Further refinement may be possible in the future, but I'm doing this small rewording now to avoid potentially confusing inaccuracy. --- doc/using-notebooks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/using-notebooks.md b/doc/using-notebooks.md index d52795ff..1c02b23d 100644 --- a/doc/using-notebooks.md +++ b/doc/using-notebooks.md @@ -82,7 +82,7 @@ notebook), JupyterLab heeds the `raises-exception` cell tag, printing a traceback but continuing execution with the next cell. In contrast, the `vscode-jupyter` extension does not yet do so. -Eventually this will be fully fixed in `vscode-jupyter`, at which point VS Code +Eventually this may be fully fixed in `vscode-jupyter`, at which point VS Code may become the best way to work with the notebooks in this project. This is related to [microsoft/vscode-jupyter#11441](https://github.com/microsoft/vscode-jupyter/issues/11441).