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

Avoiding Jupyter autosave files #48

Open
ljlamarche opened this issue Nov 22, 2019 · 2 comments
Open

Avoiding Jupyter autosave files #48

ljlamarche opened this issue Nov 22, 2019 · 2 comments

Comments

@ljlamarche
Copy link
Contributor

Jupyter notebooks autosave to .ipynb_checkpoints, however, it seems to default to whatever the last directory you clicked on is. I'm not entirely clear on the expected behavior, but it creates issues when I'm browsing mounted data and jupyter puts an .ipynb_checkpoints directory in a data directory. Later, if I run code that tries to walk through that data directory, it finds .ipynb_checkpoints, which causes an error and forces me to manually go and delete that file. It looks like you can customize the checkpoint directory (jupyterlab/jupyterlab#5809) when starting jupyter, so maybe that's something we want to consider adding as part of starting jupyter lab?

@asreimer
Copy link
Contributor

asreimer commented Nov 24, 2019

It looks like any time you try to do anything in Jupyterlab (terminal, text editor, notebook, etc), it creates that checkpoints hidden directory. If you set the directory location, there's a bug where it will overwrite checkpoints when you have several notebooks/files with the same name: jupyterlab/jupyterlab#5809 (comment)

Something to keep an eye on, but I'm hesitant to hardcoding the checkpoint directory ourselves because of that bug.

Here's the issue tracking this problem: jupyter/notebook#4645. Hasn't been fixed yet.

@asreimer
Copy link
Contributor

Still unresolved in jupyter/notebook.

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

No branches or pull requests

2 participants