Split start_new_kernel_client into kernel and client creation #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 tocreate_kernel_manager
(see Rename start_kernel_manager into create_kernel_manager #92).self.owns_km
indicates if the kernel manager is created by theNotebookClient
or if it is passed from outside. If theNotebookClient
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).