fix: reset example notebook kernelspec to python3 - #1254
Open
kylebarron wants to merge 1 commit into
Open
Conversation
Jupyter records the last kernel that ran a notebook in its metadata, so saving from a locally-registered kernel (e.g. one pointing at this repo's .venv) persists that kernel's name into the committed file. JupyterLab resolves that saved name against the full kernel search path, and the user-level kernel directory stays on that path even though `juv run` prepends its ephemeral environment via JUPYTER_PATH. A notebook stamped with a machine-specific kernel therefore executes in that kernel's environment rather than the one `juv run` built from the notebook's PEP 723 metadata, and its declared dependencies appear to be missing. Reset the 18 affected notebooks to the generic `python3` kernelspec, whose argv is a bare `python` and so inherits whichever environment launched Jupyter. Add a pre-commit hook so a future save can't reintroduce it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Jupyter records the last kernel that ran a notebook in its metadata, so saving from a locally-registered kernel (e.g. one pointing at this repo's .venv) persists that kernel's name into the committed file.
JupyterLab resolves that saved name against the full kernel search path, and the user-level kernel directory stays on that path even though
juv runprepends its ephemeral environment via JUPYTER_PATH. A notebook stamped with a machine-specific kernel therefore executes in that kernel's environment rather than the onejuv runbuilt from the notebook's PEP 723 metadata, and its declared dependencies appear to be missing.Reset the 18 affected notebooks to the generic
python3kernelspec, whose argv is a barepythonand so inherits whichever environment launched Jupyter. Add a pre-commit hook so a future save can't reintroduce it.