Instead of a single file, have a backend that treats a directory like a notebook. This will allow us to:
Separate the output into separate files and keep the .ipynb clean and diffable
Allow to include other python/data as part of the notebook itself.
I notice that this is compatible with Gist as well. We could reconstitute the ipynb into input and output, and then add the other non-asset files into the gist.
I think for brevity, the output to Gist wouldn't have separate output files. So this wouldn't be a gist backend per se, just something that can export/import to gist. The import process would be fairly straightforward as well.
dalejung
commented
9 years ago
Instead of a single file, have a backend that treats a directory like a notebook. This will allow us to:
.ipynbclean and diffableI notice that this is compatible with Gist as well. We could reconstitute the
ipynbinto input and output, and then add the other non-asset files into the gist.I think for brevity, the output to Gist wouldn't have separate output files. So this wouldn't be a gist backend per se, just something that can export/import to gist. The import process would be fairly straightforward as well.