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

ipdb with separate kernel/client pushing stdout to kernel process only #2297

Closed
rabbitmcrabbit opened this issue Aug 13, 2012 · 1 comment
Closed
Milestone

Comments

@rabbitmcrabbit
Copy link
Contributor

Hey guys -- once again, ipython is awesome.

I'm launching ipython kernel in one terminal, and then connecting either a console or a qtconsole in a separate terminal (so that I can use vim-ipython). However, when I use ipdb.set_trace(), the initial traceback and the output of all my interactive commands are displayed on the kernel terminal rather than the console/qtconsole. I'm not getting this problem with vanilla pdb.

@minrk
Copy link
Member

minrk commented Aug 13, 2012

ipdb is not actually part of IPython, so you might want to bring this up over there.

The issue is actually this call to update_stdout, which shouldn't be made.

You can use IPython's debugger from IPython, rather than via ipdb:

from IPython.core.debugger import Tracer
t = Tracer()
t()

@minrk minrk closed this as completed Jan 20, 2013
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

No branches or pull requests

2 participants