Skip to content
This repository

double pylab greeting with c.InteractiveShellApp.pylab = "tk" in zmqconsole #1170

Closed
juliantaylor opened this Issue December 17, 2011 · 7 comments

3 participants

Julian Taylor Fernando Perez Min RK
Julian Taylor
Collaborator

I added c.InteractiveShellApp.pylab = "tk" to my config to get pylab with the zmqconsole.
you then get two pylab greetings when you start it:

ipython console
Welcome to pylab, a matplotlib-based Python environment [backend: TkAgg].
For more information, type 'help(pylab)'.
[IPKernelApp] To connect another client to this kernel, use:
[IPKernelApp] --existing kernel-3395.json

Welcome to pylab, a matplotlib-based Python environment [backend: TkAgg].
For more information, type 'help(pylab)'.

adding only c.TerminalIPythonApp.pylab = "tk" to the config will give you one greeting but pylab won't work which is a bit confusing.

Fernando Perez
Owner

This will be solved by a refactoring: there should be a single kernel object anywhere and then a single frontend object a local client would be a frontend with an in-process kernel.

I hope to get to make that big cleanup in the spring.

Min RK
Owner

This is a minor oversight in the two-process frontend, which inherits from the Terminal application, but doesn't override init_gui_and_pylab() to be a no-op.

Fernando Perez
Owner

Do you want to take a stab at fixing it? An eventual refactor will make this impossible by construction, but for now doing overrides in the subclasses is necessary and we alrady do it in multiple places, so we might as well ship 0.12 without this issue...

Min RK
Owner

Sure, it's two lines, PR incoming

Fernando Perez
Owner

great!

Min RK
Owner

PR #1173

Fernando Perez fperez closed this in c8874d7 December 17, 2011
Fernando Perez
Owner

Awesome, reviewed and merged (keeping the merge handle as per our new approach :) Thanks!

Fernando Perez fperez referenced this issue from a commit January 10, 2012
Commit has since been removed from the repository and is no longer available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.