bpo-36388: fix Pdb.do_debug to not trace itself#23202
bpo-36388: fix Pdb.do_debug to not trace itself#23202blueyed wants to merge 1 commit intopython:mainfrom
Conversation
This adopts `Pdb.do_debug`, given there are fixes in there already, and it is not trivial to "patch out" the wrong `sys.settrace` in there easily. Ref: https://bugs.python.org/issue36388 Ref: python/cpython#23202
This adopts `Pdb.do_debug`, given there are fixes in there already, and it is not trivial to "patch out" the wrong `sys.settrace` in there easily. Ref: https://bugs.python.org/issue36388 Ref: python/cpython#23202
This adopts `Pdb.do_debug`, given there are fixes in there already, and it is not trivial to "patch out" the wrong `sys.settrace` in there easily. Ref: https://bugs.python.org/issue36388 Ref: python/cpython#23202
This adopts `Pdb.do_debug`, given there are fixes in there already, and it is not trivial to "patch out" the wrong `sys.settrace` in there easily. Ref: https://bugs.python.org/issue36388 Ref: python/cpython#23202
|
This PR is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
|
This is still legit, but only missing review and a test. |
asvetlov
left a comment
There was a problem hiding this comment.
The patch looks good.
NEWS entry and tests are needed.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
|
This PR is stale because it has been open for 30 days with no activity. |
|
Ping, @blueyed -- is this still something you're interested in working on? :) |
|
Closing as it is stale, if you want to work on this, the PR can be re-opened or a new PR can be created. |
https://bugs.python.org/issue36388