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

Close notebook after execution #479

Closed
Nikolai-Hlubek opened this issue Mar 13, 2020 · 5 comments
Closed

Close notebook after execution #479

Nikolai-Hlubek opened this issue Mar 13, 2020 · 5 comments

Comments

@Nikolai-Hlubek
Copy link

When I run papermill.execute_notebook() the executed notebook stays in memory and occupies space until I close the parent notebook.

Is there a way to close the notebook after the execution, while the parent notebook is still running?

@MSeal
Copy link
Member

MSeal commented Mar 19, 2020

Are you referring to the subprocess continuing to alive after execution is completed? I believe jupyter/nbclient#34 fixes the upstream issue with the child process staying open after execution. That should be resolved with the 0.2 release of that package once that merges.

Reverting to papermill 1 should also resolve the issue until papermill 2.0's new dependency fixes the problem.

@Nikolai-Hlubek
Copy link
Author

Yes I think I'm experiencing this issue.
I didn't dig deep enough to see that you already fixed this. Thanks a lot.

I'll check if it works once the new release comes out.

@MSeal
Copy link
Member

MSeal commented Mar 31, 2020

@Nikolai-Hlubek it took a bit longer, but try install papermill 2.1 (or nbclient 0.2) and the issue should be resolved now.

@Nikolai-Hlubek
Copy link
Author

Thanks @MSeal. It works like a charm now.

Pushed 332 jobs through the pipeline and had no issues.

@MSeal
Copy link
Member

MSeal commented Apr 13, 2020

Awesome! Glad it resolved the issue.

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