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

Rip out caching machinery and prepare for new Jupyterlab. #101

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

thetorpedodog
Copy link
Contributor

We ran into a problem when deleting a notebook and creating a new one of the same name. We believe this might be related to caching. Even if it isn't, the caching system is no longer particularly useful.

This change removes the caching machinery, and at the same time fixes several bugs and prepares us for the next version of Jupyterlab, which will require contents plugins to include the hash of the notebook file when reading it (i.e., everything that needed to be done to make it work on a freshly-installed Jupyterlab venv).

We ran into a problem when deleting a notebook and creating a new one
of the same name. We believe this might be related to caching. Even if
it isn't, the caching system is no longer particularly useful.

This change removes the caching machinery, and at the same time fixes
several bugs and prepares us for the next version of Jupyterlab, which
will require contents plugins to include the hash of the notebook file
when reading it (i.e., everything that needed to be done to make it work
on a freshly-installed Jupyterlab venv).
@antalakas
Copy link
Collaborator

[sc-51518]

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

Successfully merging this pull request may close these issues.

2 participants