quarto-dev / quarto-dev/quarto-cli
Feature request: per cell cacheing for python cells
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
From the documentation site:
Note that for Jupyter, the cache for a document is invalidated if any of the code blocks change. For Knitr, invalidation occurs on a per-cell basis. (emphasis added)
It would be great it adding or modifying 1 python cell only invalidates the cache for that specific cell, rather than re-executing all code cells. This would be really nice if you wanted to say add a new plotting cell but don't want to rerun expensive computations in previous cells
I'm not sure if this is a limitation of jupyter-cache or if there are plans to support this in the future. Or maybe allow usage or incorporation of a different caching library, e.g. like ipycache
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the documentation statement about Jupyter cache invalidation, then investigate the referenced jupyter-cache and ipycache projects to determine where this behavior is implemented or limited. Done means adding or modifying one Python cell invalidates only that cell's cache instead of re-executing all code cells.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, jupyter-notebook, python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100