➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: "pdb.Pdb(skip=…).set_trace()" should always stop on calling frame
Type: behavior Stage: patch review
Components: Library (Lib) Versions: Python 3.9, Python 3.8, Python 3.7, Python 3.6, Python 3.5, Python 2.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: blueyed
Priority: normal Keywords: patch

Created on 2019-11-15 00:26 by blueyed, last changed 2022-04-11 14:59 by admin.

Pull Requests
URL Status Linked Edit
PR 17159 open blueyed, 2019-11-15 00:29
Messages (1)
msg356638 - (view) Author: daniel hahler (blueyed) * Date: 2019-11-15 00:26 
The following will not stop for debugging:

    python3.8 -c 'import pdb; pdb.Pdb(skip=["__main__"]).set_trace()'

The example is contrived, the real case would be to have some "noisy" module being excluded in general, but when you add an explicit "set_trace()" in there it should still stop there, and not on some upper frame.

This was changed a long time already in https://github.com/python/cpython/commit/313a7513b0c5771042d850d70782a2448d1cdcb7 (Python 2.3), but it is not really clear.

I will create a PR reverting that part and see how it goes.
History
Date User Action Args
2022-04-11 14:59:23adminsetgithub: 82987
2019-11-15 00:29:14blueyedsetkeywords: + patch
stage: patch review
pull_requests: + pull_request16668
2019-11-15 00:26:53blueyedcreate