[New-bugs-announce] [issue38806] "pdb.Pdb(skip=…).set_trace()" should always stop on calling frame
daniel hahler
report at bugs.python.org
Thu Nov 14 19:26:53 EST 2019
New submission from daniel hahler <python-bugs at thequod.de>:
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.
----------
components: Library (Lib)
messages: 356638
nosy: blueyed
priority: normal
severity: normal
status: open
title: "pdb.Pdb(skip=…).set_trace()" should always stop on calling frame
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38806>
_______________________________________
More information about the New-bugs-announce
mailing list