Handle missing Jupyter kernelspecs gracefully - #219
Draft
Erotemic wants to merge 1 commit into
Draft
Conversation
Distinguish installed Jupyter libraries from an executable kernel, allow notebook construction without a registered kernelspec, and skip only execution-dependent tests. Co-authored-by: GPT-5.6 High <noreply@openai.com>
Erotemic
force-pushed
the
review/notebook-kernel-robustness
branch
from
July 12, 2026 03:44
6f95fd0 to
2797501
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
Root cause
The test suite assumed that importing Jupyter packages implied a registered
python3kernelspec, causingNoSuchKernelfailures in otherwise valid environments.Validation
mypy,ty, fatal flake8 selectors, andgit diff --checkpassed.