-
Notifications
You must be signed in to change notification settings - Fork 428
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
Comments
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. |
Yes I think I'm experiencing this issue. I'll check if it works once the new release comes out. |
@Nikolai-Hlubek it took a bit longer, but try install papermill 2.1 (or nbclient 0.2) and the issue should be resolved now. |
Thanks @MSeal. It works like a charm now. Pushed 332 jobs through the pipeline and had no issues. |
Awesome! Glad it resolved the issue. |
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?
The text was updated successfully, but these errors were encountered: