Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for input/output caching #76

Open
breandan opened this issue May 29, 2020 · 3 comments
Open

Support for input/output caching #76

breandan opened this issue May 29, 2020 · 3 comments

Comments

@breandan
Copy link
Contributor

Similar to the Python kernel, it would be nice to support input/output caching. Is it possible to access the contents of other cells programmatically?

@ileasile
Copy link
Collaborator

Hello @breandan! Yes, you can. res1, res2 etc. will do the thing

@ileasile
Copy link
Collaborator

ileasile commented May 29, 2020

Ah... Inputs/outputs caching is not supported. Only results are saved.

@altavir
Copy link
Contributor

altavir commented May 31, 2020

@ileasile I failed to access results by resX. Is there a documentation for that? Also I agree with @breandan here, it will be nice to have. As I mentioned in another issue, beakerX has this feature and it is rather powerful. What we would like to have is the "reflective" access to both cell content and cell output via cell unique identifier. In the end we would like to have full control like executing other cells and external API artifact for that so we could easily write new notebook plugins with custom functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants