-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
Unable to run kernel #40
Comments
logconfig is a bit weird, since that's not part of ipykernel or anything ipykernel imports, to my knowledge. Can you start notebooks in a different directory? |
I'm getting a similar thing without reference to logconfig:
Update: mine seems to have been caused by an old system ipython package from Ubuntu and worked after removing all the old ipython/ipython-notebook packages and reinstalling them via pip |
I had the same problem after installing matplotlib. I had to uninstall both matplotlib and ipython/ipython notebooks, and reinstall with |
@sorrelh what do you get from |
...and |
I ran into the same problem multiple times. It seems that it stems from the fact that I had ipython installed through both apt and pip. |
Thanks, I think apt and setuptools frequently confuse each other. It's unfortunate how often this happens. |
I am having the same problem. I installed Python 2.7 using Anaconda, and can run Jupyter notebook with no problems. I just used Anaconda to make a new, concurrent, Python 3.5 installation along with Jupyter (I went through the correct procedure for maintaining the two versions of Python at once), and I receive an error when opening a notebook using the 3.5-kernel. C:\Anaconda\envs\py35\python.exe: Error while finding spec for 'ipykernel.__main __' (<class 'ImportError'>: DLL load failed: The specified module could not be f ound.); 'ipykernel' is a package and cannot be directly executed |
I have the same issue now. Don't know how to solve.. |
I have an |
I have a similar problem, but in my case the import error is with decorator. Is a new virtualenv instalation with python 3.4.3. Any idea to solve this? [I 04:13:00.279 NotebookApp] Kernel started: dd3938af-5112-4158-87b6-a93a41fdcc9a |
@ellisonbg does |
I create a new virtualenv and reinstall. Now works!!! |
I had the same problem -- turned out it was because I had a file in the same folder written in Python 2 (when my ipython notebook was running Python 3). Changing the extension of that file to .txt fixed the issue for me. |
Seems I hit the same issue because I'd re-initialised a Python 2.7 virtualenv with Python 3.5. Starting from a clean virtualenv solved the issue. |
I had the same error, using Python v3.4.3 with Jupyter (v4.x) on Ubuntu GNU/Linux. I couldn't solve this problem, but then I noticed that, in the same folder I was running |
I'm having a similar problem after having to install with pip. Unfortunately, pip doesn't know what I'm talking about when I ask it to install something called If there are known issues with installing matplotlib etc. before ipython notebook, it would be great if someone would write those up with the recommended order of installation. I'd prefer to use anaconda, but in this case I don't have that option. |
The package you need to ask pip to install is 'path.py'. There's no neat
way to find that out, though, it's just something I know.
|
Hi, I'm having a similar problem with Jupyter 4.1.0. Specifically: |
@cranmer a |
Having the same issue I had installed new ipywidgets and then went into a spiral, did my best to nuke all prior installations since I've been using this stuff so long figured the upgrade combinations had finally hit me so I cleaned house and now I have Jupyter up and going via P3 and the p3 kernel is fine but my p2 kernel won't start. fwiw I did also uninstall and reinstall the ipywidgets and started to get errors on the nbextensions not being found (yet they are working) so far I'm not seeing the widgets, but that is a different issue. I have verified that path.py is installed for p2.. So anyhow I'm left with this when trying to start a P2 notebook:
Grrrrr.... |
This message typically means it's finding an older version of the |
@takluyver Thanks for following me through this travale..I did remove the system installed Ipython via APT I also reinstalled using:
and that changed the error message for the p2 kernel to
|
😕 Don't know about that one, sorry. I'd suggest trying to work out where it thinks it's importing IPython from - there might be a broken install lying around somewhere. |
somehow I seem to have broken ipython (2) quite completely, any ideas how to start over? If I even just try to start ipython from the command prompt I get:
..... and at the end
And I have checked to see if they are installed via pip and they claim to be yet also if I start the interpeter i cannot import ipython (no such module) Any ideas? where how to fix? |
What's the shebang ( |
I have not directly accessed $PYTHONPATH (don't directly know how!)
|
is this an issue?
|
No, that's fine, PYTHONPATH generally shouldn't be present unless you know you need it. I was checking that it wasn't set. Does the list pip gives you also include |
Weird pip list did not show it I did pip install, it said requirement already satisfied, did pip unintsall, it did a bunch the reinstalled no pip list shows it. now Ipython starts from command line (improvement but new error message on Jupyter
So maybe install that? |
Yup, install that... I wonder if you have an old version of pip - try running:
|
Ok I'm almost there I ended up installing pip install jupyter, now the jupyter shebang in bin points at python (which is python 2) the remaining jupyter files in bin are set to p3 I did run pip3 install jupyter after the pip install, hoping that would fix what gets executed from the command line? it seems the whole mess related to confusion between the two installations? both p2 and p3 kernels are running but I'm back to errors in the console... which don't seem to be hurting but still.... |
You shouldn't need The |
Well I was getting an error message from p2 start up complaining about other jupyter components after I fixed Jupyter-client which was why I went ahead with installing core... it "seems notebook running with p3 that is where the shebang for that points.. |
Rats, you're right, the |
so... solution? and I guess open bug? not real sure what is running what given the mix of p2/p3 components in bin... |
Opened jupyter/jupyter_core#76 about it. I don't think it should interfere with what you're trying to do, though. The notebook server should still be running on Python 3, it's just extra confusing. |
Thanks so much! whew! I suspect it may be involved with some of the other misc errors? but strange though.. for the time being, I'm good! |
Been having the same dead kernel issue when launching jupyter notebook. pip install "ipython[notebook]" --upgrade resolves my issue |
How I fixed it! I had made a custom package called Check if you have any packages in the folder from where you are starting your jupyter notebook. |
Having the same issue and still don't know how to fix yet. I followed the steps here, Step 1 goes fine, but Step 2 gives an error:
|
Hi all, I kind of have the same problem when I try to start a root notebook with C++ kernel. The output I get is the following: KernelRestarter: restarting kernel (2/5) I would be grateful for any kind of help! |
… when using ipython3) See (epc:pop-to-last-server-process-buffer) and ipython/ipykernel#40
When I try to open a notebook using the Python 3 kernel, I get the following output.
I am using IPython, Jupyter and ipykernel v4.0.3 with Python 3.4.3 on Linux.
Linux kommandcenter 4.1.5-1-MANJARO #1 SMP PREEMPT Tue Aug 11 05:14:23 UTC 2015 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: