Thank you. This worked for me. I didn't realize it was an IPython command. 
I did try Ctrl+. in Spyder before posting here, but I guess the focus must 
not have been in the IPython window because nothing happened the first time 
I tried it.

On Saturday, October 11, 2014 3:03:46 PM UTC-4, Adrian Klaver wrote:
>
> On 10/11/2014 11:06 AM, Stack CopyrightX wrote: 
> > The Canopy python IDE has a simple command (Ctrl+.) that is reached 
> > using the menus with Run->Restart Kernel... 
>
> Actually this is a IPython command: 
>
> http://ipython.org/ipython-doc/stable/interactive/qtconsole.html 
>
> Process Management 
>
> With the two-process ZMQ model, the frontend does not block input during 
> execution. This means that actions can be taken by the frontend while 
> the Kernel is executing, or even after it crashes. The most basic such 
> command is via ‘Ctrl-.’, which restarts the kernel. This can be done in 
> the middle of a blocking execution. The frontend can also know, via a 
> heartbeat mechanism, that the kernel has died. This means that the 
> frontend can safely restart the kernel. 
>
> > 
> > This forces the IDE to keep history and things like that, but to restart 
> > the python kernel (would it also be correct to say the python 
> > *interpreter*? or is kernel different from interpreter in this context?) 
> > so that all existing variables in memory and function definitions are 
> > flushed, allowing me to start with a clean kernel. 
>
> The kernel they are referring to is the IPython kernel. 
>
> > 
> > Is there some way to do this in Spyder? 
>
> Yes, enter Ctrl + . in the IPython console. 
>
> > 
>
>
> -- 
> Adrian Klaver 
> [email protected] <javascript:> 
>

-- 
You received this message because you are subscribed to the Google Groups 
"spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.

Reply via email to