-
Notifications
You must be signed in to change notification settings - Fork 147
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
Connect to an existing kernel #267
Comments
|
I found a workaround is to use |
I am not a regular Jupyter user so I am afraid I cannot really help. Nevertheless, can you detail what you mean by using ipdb in jupyter ? |
I guess that the (Similarly, |
The same way, I guess that the |
You are correct. According to the information found at jupyter/qtconsole#143 and jupyter/qtconsole#99, it appears that this is an open problem. Thank you for sharing your insight, and I apologize for opening this here |
Possible to attach ipdb to an existing kernel?
Currently, ipdb starts a new kernel session each time it is called, which can be inconvenient and time-consuming. If ipdb could connect to an existing kernel session, it would be much more efficient for debugging.
I believe this feature would be useful for many developers who use ipdb in conjunction with Jupyter notebooks or other interactive environments.
The text was updated successfully, but these errors were encountered: