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 restart kernel #326

Open
JosephP91 opened this issue Mar 4, 2019 · 1 comment
Open

Avoiding restart kernel #326

JosephP91 opened this issue Mar 4, 2019 · 1 comment
Labels

Comments

@JosephP91
Copy link

Hello everybody. I was wondering if there is a way to avoid starting a new kernel every time a notebook execution is requested.

@MSeal
Copy link
Member

MSeal commented Mar 5, 2019

Since there's no server managing kernel lifecycles you'd need some extended architecture to lean against to launch and reap kernels. To plug into that architecture you'd need to register a custom engine which skips nbconvert's kernel launch step and connects directly with some target kernel that's already alive.

Generally this won't be supported in native papermill except to well established remote systems like kernel gateway (see: #303). If there's a system you'd like to have native extensions to, we're always happy to help guide how to add it to papermill or suggest how to embed custom extensions for less general use-cases.

@MSeal MSeal added the question label Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants