Skip to content
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

Two-process terminal frontend #708

Closed
wants to merge 23 commits into from
Closed

Two-process terminal frontend #708

wants to merge 23 commits into from

Conversation

minrk
Copy link
Member

@minrk minrk commented Aug 17, 2011

This extends #433 to use TerminalInteractiveShell/TerminalIPythonApp subclasses, so all our configuration, etc. is inherited as you would expect.

Not ready for merge because, among other things, ctrl-C crashes the kernel. Mostly posted as a starting point for someone else to take over finishing this client.

As far as I can tell, it's already quite functional as long as you never hit ctrl-C :).

omazapa and others added 23 commits August 17, 2011 00:23
this does a lot of the boiler plate for us, so Omar's communication
code is used in place of run_cell / complete.

Now colors, prompts, indentation, cl-args, etc. are all inherited
from regular existing code.

keyboard interrupts don't work yet, the kernel just dies...
@ivanov
Copy link
Member

ivanov commented Oct 8, 2011

this would be really nice to get back plain terminal ipython with the two-process connection capability. For one, it would enable Django-shell embedding to work with vim-ipython in a simlpe and straightfoward manner - which was recently requested in ivanov/vim-ipython#11 and I pointed them to this PR.

@ivanov
Copy link
Member

ivanov commented Oct 13, 2011

closing this one, since #864 will supersede it as

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants