Closed mwouts closed 2 years ago
The long string seems to be VS Code's way to store Javascript outputs. The list of strings is compliant with Jupyter Lab's export, so maybe the failing display of notebooks executed with either jupytext or nbconvert in VS Code is due to a non-standard handling of outputs in VS Code.
Now, when I open a notebook executed with Jupytext or NBconvert (same outcome) in Jupyter Lab, the outputs for the first cell are displayed as
<IPython.core.display.Javascript object>
and the interactive tables just show "Loading ...". This appears to be a different issue - the notebook is not trusted so Javascript is not allowed. This is fixed when I execute "View / Activate Command Palette / Trust Notebook" in Jupyter Lab, probably because executing the notebook with either Jupytext or NBconvert does not add it to the list of trusted notebooks.
For instance, if I run
on this document, and then open the resulting
.ipynb
file, no interactive table is displayed.If I open and re-execute the notebook in another editor (here VS Code), the interactive tables works. The diff between the version generated by
jupytext --execute
and VS Code is limited to the outputs of theinit_notebook_mode
cell:The version that fails has a list of string in "application/javascript"
while the version that works has a single string in "application/javascript":