-
Notifications
You must be signed in to change notification settings - Fork 5k
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
No module named ipykernel #1558
Comments
Did you close the issue because you resolved the problem? |
Yes, I've created |
OK, great. |
I have the same issue here, but am unclear as to how it was fixed. To be clear, I need to manually create |
OK, I did not have |
I installed Anaconda with py2.7. now i have the exact same issue but cant solve it, how can I created kernel.jason file with path to virtualenv?? |
thank you |
Similar case but not same, Simply installing ipykernel worked for me.
|
I had the exact same issue. I used the following commands to fix this. source activate <ANACONDA_ENVIRONMENT_NAME> |
I got this error when I use the jupyter notebook.
The env already install ipykernel
How do I fix this problem? |
Worked perfectly. Thank you @nikhilpriyatam |
Thanks @takluyver for the resource. |
I'm stumped. I'm getting the following error.
However, I'm able to do the following.
My
I'm even able to run the exact ipykernel command!
It's just that when jupyter tries to run that exact command, it's hitting that error 🤷 |
I think I've found the root cause, though not the solution yet: the python3.7 in the venv environment is symlinked to /usr/local/bin/python3.7, still they have different sys.path, see below: local python3.7 works
It's a link of /usr/local/bin/python3.7
Running that python3.7 won't import the same path:
|
Ok, here it goes: I've had a previous - global - installation is jupyter and just switched to venv based install and because of that,
Kudos to nteract/hydrogen#1824 for letting me know about |
I'm solved this problem by restart the cmd |
@ebanner I was having the exact same issue as you, trying to use a pyenv environment inside jupyter. Everything seemed fine from the python shell and I could even run the command manually like you did. I eventually found that if I started my notebook with my default kernel and checked "sys.path", it was listing some old version of python I had installed via hombrew and that was messing everything up and preventing my pyenv python versions from running jupyter. I uninstalled the brew version of python, removed any existing versions of jupyter, reinstall jupyter and now everything is working as expected. |
ubuntu if
doesn't work, then try to use |
Thanks @ebanner, @zoltansx, and @acdifran for the detailed write-ups. In my case, I did I was able to resolve it by deleting the Python 3.8 virtual environment, creating a new one with Python 3.6 from pyenv, then installing and running FWIW, I don't think it's necessary for the Python versions to be identical between the Jupyter virtual environment and the kernel virtual environment. For example, on another device, my Jupyter virtual environment is running Python 3.8, but it's from pyenv (i.e., not the macOS default), and that's able to run notebooks from the pyenv Python 3.6 virtual environment. |
I've installed jupyter via pip in virtualenv with python3.5. When I create new notebook I get an error:
How to fix this?
My
pip list
:P.S. I'm using OS X 10.11.5
The text was updated successfully, but these errors were encountered: