[IPython-dev] What causes the kernel to stay busy?

Eric Firing efiring at hawaii.edu
Fri Dec 12 16:40:58 EST 2014

On 2014/12/12, 11:27 AM, Tony Cappellini wrote:
> Message: 3
> Date: Thu, 11 Dec 2014 22:55:23 -1000
> From: Eric Firing <efiring at hawaii.edu <mailto:efiring at hawaii.edu>>
> Subject: Re: [IPython-dev] What causes the kernel to stay busy?
> To: ipython-dev at scipy.org <mailto:ipython-dev at scipy.org>
> Message-ID: <548AAD7B.7040600 at hawaii.edu
> <mailto:548AAD7B.7040600 at hawaii.edu>>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>I wasn't paying attention to which list this was addressed to--I thought
>>> was anaconda.  Regardless of whether you are using anaconda, the
>>>answer is the same: you need IPython 2.3 or higher
> Python 2.7.8 (default, Oct 15 2014, 22:04:42)
> Type "copyright", "credits" or "license" for more information.
> IPython 2.3.1 -- An enhanced Interactive Python.
> ?         -> Introduction and overview of IPython's features.
> %quickref -> Quick reference.
> help      -> Python's own help system.
> object?   -> Details about 'object', use 'object??' for extra details.
> After updating to iPython 2.3.1 and entering a few python statements
> into the notebook, it looks like the kernel busy issue still persists.
If you enter the same statements at a raw Python terminal prompt, does 
it remain responsive?  And if so, what about if you do it in a plain 
IPython console?  (Is the problem notebook-specific?)

What is the simplest sequence of commands that triggers the hang?

I probably won't be able to offer any suggestions, but if anyone else 
has an idea, they probably will want the answers to the above questions.

Also, it's possible I was wrong about the version at which app-nap 
handling was introduced; but updating to the latest release is a good 
first step in troubleshooting in any case.


More information about the IPython-dev mailing list