Adopt nextgen-kernels-api for kernel client management #170
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.
Overview
This PR replaces the custom kernel client implementation in
jupyter-server-documentswith nextgen-kernels-api, a more extensive and reusable implementation of the Jupyter kernel protocol.Key Changes
kernels/directory and associated tests)nextgen-kernels-api >= 0.6.0Why nextgen-kernels-api?
The
nextgen-kernels-apilibrary aims to provide a robust, well-tested kernel client implementation that:jupyter-server-documentsdepends on a stable interfacejupyter-server-documentscan leverage the same kernel client implementationThere's an open discussion about moving
nextgen-kernels-apiinto thejupyter-ai-contriborg: https://github.com/orgs/jupyter-ai-contrib/discussions/5Technical Details
The PR:
MultiKernelManagerandKernelManagervia traitlets to useDocumentAwareKernelClientmsg_types,exclude_msg_types) to route messages efficientlyTesting
All existing tests pass. The custom kernel tests were removed as they tested implementation details now handled by
nextgen-kernels-api.Diff stats: 24 files changed, 294 insertions(+), 1981 deletions(-)