Change register-kernel to manual kernel registration #7
Conversation
This file contains 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
appleparan
changed the title
appleparan
changed the title
* Why: Automatic registration has an incorrect assumption that jupyter must be installed globally * Remove batch script for adding jupyter kernels * Remove after_install hook because it is redundant now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It fixes #1 and #2 .The actual cause of this bug is the incorrect assumption that
jupytermust be installed in the global versions. So, instead of automatically updating the kernel in all existing virtualenvs, I changed it to manually register the kernel usingregister-kernel.It might resolve #6, too.
Pros
Cons
pyenv register-kernelafterpip install jupyterby yourself.