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

Split start_new_kernel_client into kernel and client creation #94

Merged
merged 1 commit into from
Aug 9, 2020
Merged

Split start_new_kernel_client into kernel and client creation #94

merged 1 commit into from
Aug 9, 2020

Conversation

davidbrochart
Copy link
Member

Separates (async_)start_new_kernel_client into:

  • (async_)start_new_kernel: starts a new kernel.
  • (async_)start_new_kernel_client: starts a new client of the kernel.

This gives more flexibility as to creating the kernel and/or the client from outside. Internally, both methods are called so it doesn't change anything.

Also in this PR:

  • start_kernel_manager renamed to create_kernel_manager (see Rename start_kernel_manager into create_kernel_manager #92).
  • self.owns_km indicates if the kernel manager is created by the NotebookClient or if it is passed from outside. If the NotebookClient owns the kernel manager, the cleanup of the kernel (client and manager) will be done by default. If not, the cleanup won't be done by default (previously, it was always done by default).

Copy link
Contributor

@MSeal MSeal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the separation of concerns into clearly labeled functions.

@MSeal
Copy link
Contributor

MSeal commented Jul 30, 2020

I'll wait for Sylvain to take a look to merge

@MSeal
Copy link
Contributor

MSeal commented Aug 9, 2020

Going to merge since it's been a bit without other input

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.

None yet

2 participants