You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
blueyedmannequin opened this issue
Mar 31, 2019
· 4 comments
Labels
3.9only security fixes3.10only security fixes3.11bug and security fixesstdlibPython modules in the Lib dirtype-bugAn unexpected behavior, bug, or error
bdb.Bdb.set_trace should set "f_trace_lines = True" on frames explicitly.
Otherwise they might be skipped if something else has set it to False already, e.g. via a suggested change for coverage.py to set this for performance reasons (nedbat/coveragepy#791).
Coverage.py now sets f_trace_lines=0 when it doesn't want to trace, and I've started getting bug reports that this breaks tests using pdb: nedbat/coveragepy#1402. Can we move this forward?
3.9only security fixes3.10only security fixes3.11bug and security fixesstdlibPython modules in the Lib dirtype-bugAn unexpected behavior, bug, or error
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
Linked PRs
f_trace_lines = Trueon all frames uponpdb.set_trace()#110881The text was updated successfully, but these errors were encountered: