Matthias Mittner

Thanks for the effort, I will review the code in detail once I find the time. Can you check why the travis builds fails for the PR?

Nice idea. I can do the reviewing/merging. How would we handle choosing the backend? We could either parse the provided filename, hand over an option to the `cache`-magic or allow...

ok, so the hierarchy is: 1. explicitly provided cell-wise option 2. globally provided option 3. filename parsing Meaning that a cell-wise option beats everything else and filename-parsing is the last...

Looks interesting. We could support it as an alternative backend (under the same constraints as the others, i.e., graceful fallback in case the module fails to import etc). Let's wait...

One way to do this, is to use a script like this: https://github.com/paulgb/runipy and then let travis-ci upload the processed notebooks to a specific branch of the `ipycache`-repo. Here is...

Interesting idea! But comparing cell output to previously generated output may break when minor changes are made (could also happen when minor changes to external libraries are made?). Say we...

Example: cell 1 ``` python %%cache test.pkl a a=[i for i in range(10000)] ``` cell 2 ``` python import ipycache try: a=ipycache.load_vars('./test.pkl', ['a']) except: raise CustomErrorThatTellsUsSomething ``` Then run all...

Actually, your second test should produce exactly the same output, i.e., `Computing...\n10000`, since `ipycache` saves and loads the outputs. The only thing that should differ would be the verbosity-output, i.e.,...

Ok, but how do we define if the notebook passes the test? In a `doctest`, you have to add some code to a function that defines the test. We could...

I added a `ipynb_runner.py` script which can run the ipython notebooks from the command line. It reports if any of the cells fail (i.e., cause an exception). This PR already...