[IPython-dev] Thoughts on the notebook format for version control

Pablo Winant pablo.winant at gmail.com
Sun Nov 6 08:07:30 EST 2011


This conversation has reminded me of a nice and simple feature I have been
missing when switching from the Sage notebook to the the IPython one.
Attached to each Sage notebook is a DATA directory where the user can save
files associated with the notebook. For instance the statistical data
associated to the exploration code. Then notebooks can be exported/imported
with the DATA directory so that everything is really self-contained and
reproducible. Technically, I think everything is basically stored in a
compressed archive.
This behaviour is a bit different from the way IPython currently stores its
notebook but it is not that far from having a cache directory (or a file)
included with the saved notebook so I thought it could pertain to the same


On Sun, Nov 6, 2011 at 12:22 PM, Thomas Kluyver <takowl at gmail.com> wrote:

> One thought prompted by Fernando's comparison between .ipynbo files and
> .pyc files - Cache files cluttering up my working directory can be an
> annoyance, and this is why Python 3.2 has changed to using a __pycache__
> directory for .pyc files. If we're splitting out output into separate
> files, it might be best to put them somewhere else - perhaps in the profile
> directory, or in a subfolder if we still want it to be simple to add them
> to version control.
> Thomas
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20111106/da5832cb/attachment.html>

More information about the IPython-dev mailing list