Chris Sewell

Results 1323 comments of Chris Sewell

[scrapbook](https://github.com/nteract/scrapbook) contains (in-memory only) classes to represent a collection of notebooks [Scrapbook](https://github.com/nteract/scrapbook/blob/c736e97cb99e314c7f4a1119d0fb8426adf8a6b7/scrapbook/models.py#L314), and a single notebook [Notebook](https://github.com/nteract/scrapbook/blob/c736e97cb99e314c7f4a1119d0fb8426adf8a6b7/scrapbook/models.py#L40). Of note, is that these have methods for returning notebook/cell execution metrics (like...

This is the link to the cacheing currently implemented by @mmcky and @AakashGfude: https://github.com/QuantEcon/sphinxcontrib-jupyter/blob/b5d9b2e77fdc571c4c718e67847020625d096d6d/sphinxcontrib/jupyter/builders/jupyter_code.py#L119

Another thought I had, is to look at `git` itself and e.g. [GitPython](https://github.com/gitpython-developers/GitPython). I could conceive of something like the cache being its own small repository and when you add...

- [rossant/ipycache](https://github.com/rossant/ipycache) (last commit 2016), [SmartDataInnovationLab/ipython-cache](https://github.com/SmartDataInnovationLab/ipython-cache) (last commit 2018) are both examples of cell level magics that pickle the outputs of cells for later use. - [mkery/Verdant](https://github.com/mkery/Verdant) (last commit Oct...

As discussed with @mmcky, jupinx currently uses a static cache, housed in the Sphinx `_build` folder on an Amazon server. The build is persisted for all execution triggers (cron jobbed...

Just a note to self, in case this is issue is encountered (sqlite on NFS): jupyter/notebook#1782

Hmm, I agree with ~most of these points. > Rebuilding the complete cache may take a few minutes, but is unlikely going to be much longer. You mean re-running all...

FYI, this come up from discussion with @mmcky, @choldgraf may also be interested

Heya, I would suggest this needs to be decided as an off-shoot of high-level strategy (see e.g. #839) In particular, should we be encouraging users to work with in the...

Heya thanks @NickleDave > But as you all know better than me there's a bit of a divide between Jupyter users and contributors because of javascript Yeh I think that's...