[IPython-dev] Fwd: [SciTech] ActivePapers Python edition

Konrad Hinsen konrad.hinsen at fastmail.net
Mon Dec 9 08:28:43 EST 2013


Thomas Kluyver writes:

 > However, you can easily enough tell whether the current notebook
 > has been run through once with no editing, by comparing the list of
 > code cells to the history.

That looks good enough for my purposes. Could you give me a pointer
to how I can access the kernel's history information for doing
such a comparison?

 >     I'll probably go for 3) and see how this works out.
 > 
 > 3 sounds like the best option to me: you can save the information,
 > but it shouldn't be considered as the fixed form for later
 > calculations. Presumably ActivePapers will be able to re-run the
 > cells in order if it needs to freshen the results, without the user
 > having to manually open the notebook and execute the cells.

Yes. Well, at least that's my intention, it isn't implemented yet for
notebooks. With today's ActivePapers implementation, the command
"aptool update" will re-run all calclets whose code or output is
marked as "stale" (no longer up to date) or "dummy" (intentionally
removed to reduce the file size).

Konrad



More information about the IPython-dev mailing list