[IPython-dev] History

[Thomas Kluyver]

On 18 February 2011 19:34, Robert Kern <robert.kern at gmail.com> wrote:

> I don't mean the actual objects, just whatever is given by the
> DisplayFormatter
> system and the displayhook, i.e. whatever would get sent to a remote
> frontend.
> I'm happy to have it be an extension functionality disabled by default, but
> I do
> think that it should live in the same SQLite DB to get the references
> right.


I don't have a problem with that, although my vote does go to having it
disabled by default. It's not altogether trivial, though, because we
currently store the input before running it, so the output isn't available
at the same time. Possible ways round that:
- Keep output in a separate table, indexed in the same way as input. This is
my preferred option, because it means the main history system doesn't need
to be aware of the optional output history. There's a slightly greater
chance of a mismatch between input and output, but the indexing is simple
enough that it shouldn't be a problem.
- Store input, then execute, and update the row with output (if any) - I
don't much like the idea of doing update statements after every command.
- Store input after execution - undesirable, because a command that crashes
IPython will not be stored.
- Store input after execution only when output history is turned on - ugly
idea.

Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20110218/86d25ce4/attachment.html>