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

Tab completion inside Jupyter QtConsole ipdb shell #99

Closed
DevinBayly opened this issue Feb 16, 2016 · 4 comments
Closed

Tab completion inside Jupyter QtConsole ipdb shell #99

DevinBayly opened this issue Feb 16, 2016 · 4 comments

Comments

@DevinBayly
Copy link

Hi there,

I have just discovered that the tab completion utility seems to be offline when using tracing with ipdb but only with qtconsole of the jupyter variety. By which I mean that the ipython qtconsole still has functioning tab completion during an ipdb trace so I am curious if anyone knows how to enable this, or if this needs to become something to eventually work into a later version.

Cheers,
Devin

@takluyver
Copy link
Member

I think you're mistaken about ipython qtconsole. The Qt console has never had tab completion inside the debugger, and there's no easy way to do it. See ipython/ipython#902.

@DevinBayly
Copy link
Author

ok, I'll transfer my comment to the jupyter console issue page then?

@takluyver
Copy link
Member

I'm not quite sure what you mean.

This is an issue for all Jupyter frontends, because our messaging protocol does not know about debugging specifically. The Python debugger is just calling input() to prompt the user for the next command, and that gets passed on to the frontends as a generic 'prompt for a line of input' message. There's no completion machinery associated with that.

We have vaguely talked about adding some specialised debugging messages to the protocol, which would allow building a nicer debugger interface in Jupyter frontends. But it would be quite a lot of work, and it's not very high priority.

@wmvanvliet
Copy link
Contributor

Closing this, as it is a well known issue that first needs to be addressed in the ipython kernel itself.

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

3 participants