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

Fix settrace for recursive debugger #12659

Merged
merged 1 commit into from Oct 23, 2020
Merged

Conversation

impact27
Copy link
Contributor

Fixes #12658

Python 3.7.6 (default, Jan  8 2020, 20:23:39) [MSC v.1916 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 7.18.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: 1/0
---------------------------------------------------------------------------
ZeroDivisionError                         Traceback (most recent call last)
<ipython-input-1-9e1622b385b6> in <module>
----> 1 1/0

ZeroDivisionError: division by zero

In [2]: %debug
> <ipython-input-1-9e1622b385b6>(1)<module>()
----> 1 1/0

ipdb> debug print()
ENTERING RECURSIVE DEBUGGER
> <string>(1)<module>()

(ipdb>) q
LEAVING RECURSIVE DEBUGGER
ipdb> w
> <ipython-input-1-9e1622b385b6>(1)<module>()
----> 1 1/0

ipdb>

@Carreau Carreau added this to the 7.19 milestone Oct 21, 2020
@Carreau
Copy link
Member

Carreau commented Oct 21, 2020

oops. thanks.

@Carreau Carreau merged commit 15aaa7f into ipython:master Oct 23, 2020
2 checks passed
meeseeksmachine pushed a commit to meeseeksmachine/ipython that referenced this pull request Oct 23, 2020
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.

Recursive debugger doesn't restore trace function properly
2 participants