On 02/11/2015 04:46 AM, brendandetracey via spyder wrote:
> Well, that is what happens to me. The Kernel tab is always starting
> foremost. I tried "Reset Window Layout", restarted Spyder, and the
> problem went away. However, when I adjust the window layout back to my
> liking, it breaks again, giving the Kernel focus upon startup. I have
> attached a screenshot of my layout.
I see. Well in my setup all the consoles are grouped together and when
the IPython console is started it goes to to the top and becomes the
current console. In my previous post I forced the 'Kernel' console to
the top to get the error to trigger. In your setup it looks like the
'Kernel' console becomes the current console, until you click in one of
the others. Seems visible is not necessarily current. Also seems Spyder
does not test for the presence of other open consoles and instead errors
out on first failure. I would file a bug report, because in my mind at
least, Run should skip over the 'Kernel' console and run in the IPython one.
>
>
> On Tuesday, February 10, 2015 at 8:52:42 PM UTC-4, Adrian Klaver wrote:
>
> On 02/10/2015 11:52 AM, brendandetracey via spyder wrote:
> > Yes. If I click on either the Python or IPython console first ,
> Run does
> > operate.
> >
>
> Well, the only way I can get Run not find a console is to have the
> Python console that has the Kernel number in the tab be the
> current(foremost) console. See attached screenshot.
>
> So in your customizations did you 'hide' the consoles somehow?
>
>
> --
> Adrian Klaver
>
adrian...@aklaver.com <javascript:>