-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command line execution of a jupyter notebook fails in default Anaconda 4.1. #877
Comments
In the near term, the kernel_name (in the current environment) can be specified at the CLI:
Ideally, we'd be able to overload the kernel manager in nbconvert as we have done in the notebook. However, it looks like there is no way to override the kernel discovery of the In the case of root, we should likely not append the name... or better still, figure out a less-invasive way to do it. |
Ack, this is pretty bad. We need to figure out a much better solution to this problem. |
This issue was moved to anaconda/nb_conda_kernels#34 |
See discussion at ContinuumIO/anaconda-issues#877
Command line execution of a jupyter notebook with
jupyter nbconvert --to notebook --execute
fails after upgrading to Anaconda 4.1.On saving a jupyter ipython notebook the kernel name is changed from the conventional
python2
orpython3
to the conda specific formPython [Root]
but this is not recognised bynbconvert
.This form is also not recognised when the notebook is opened in the browser in an Anaconda 4.0 installation causing problems sharing notebooks.
The behaviour was observed on OSX/3.5 and Linux/2.7.
Explicit removal of the package
nb_conda_kernels
resolves the problem, but this package is included by default in Anaconda 4.1.The text was updated successfully, but these errors were encountered: