Compared to nbformat the outputs field of execnb remains as an array of strings (for compatability with json) instead of being squashed to a single string.
This prevents execnb from being a drop in replace for nbformat at least when using with the nbdime library.
Compared to
nbformat
the outputs field ofexecnb
remains as an array of strings (for compatability with json) instead of being squashed to a single string.This prevents
execnb
from being a drop in replace fornbformat
at least when using with thenbdime
library.For example see:
https://github.com/dleen/notebook-examples/blob/main/00_core.ipynb
The logic in nbformat for splitting/joining: https://github.com/jupyter/nbformat/blob/640a0c6830bb6dc0ef963a8caab377d89ed24c6a/nbformat/v4/rwbase.py#L26