-
Notifications
You must be signed in to change notification settings - Fork 142
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
Warning when installing and running under Jupyter 4 #31
Comments
Thanks. It shouldn't affect the working of the kernel, but we'll need to update the imports before ipython 5 comes out. |
I've been trying to install this module in the jupyter/minimal-notebook Docker image. I get a similar message to the above when installing the bash_kernel.
In my case bash is not available in the "New" dropdown menu. I'm confused as to how I can invoke this kernel on the command-line, I tried several things but none of these recognize the --kernel option.
Versions:
I also tried modifying the install.py to import ipykernel or jupyter_client but got import errors. Any suggestion? |
The console should recognise the It sounds like the kernel spec is not getting installed correctly. Can you see a |
Hi, Yes I see that the bash kernel.json was being installed So modifying my script to install with did the trick. Now I just have to automate that ... will check with docker-stacks for that Thanks. On 9 September 2015 at 20:23, Thomas Kluyver notifications@github.com
|
I should probably make an option to do a systemwide install of the kernelspec rather than a per-user install. Maybe it should even do that automatically when run as root, but I'm not sure about that. The code is already there, it's just not exposed at the command line. If you want to work on it, go for it. |
Closed by #39 |
Update the anaconda version by:
|
Here is the warning message obtained during installation:
And here is the message obtained when launching a notebook with the Bash kernel:
As far as I can tell the kernel seems to work well, however.
Thanks,
Aurelien
The text was updated successfully, but these errors were encountered: