"pdb.Pdb(skip=…).set_trace()" should always stop on calling frame

[blueyed]

BPO	38806
Nosy	@blueyed
PRs	[WIP] bpo-38806: bdb: stop_here: always stop at calling frame #17159

^{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:

assignee = None
closed_at = None
created_at = <Date 2019-11-15.00:26:53.876>
labels = ['3.7', '3.8', 'type-bug', 'library', '3.9']
title = '"pdb.Pdb(skip=\xe2\x80\xa6).set_trace()" should always stop on calling frame'
updated_at = <Date 2019-11-15.00:29:14.383>
user = 'https://github.com/blueyed'

bugs.python.org fields:

activity = <Date 2019-11-15.00:29:14.383>
actor = 'blueyed'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-11-15.00:26:53.876>
creator = 'blueyed'
dependencies = []
files = []
hgrepos = []
issue_num = 38806
keywords = ['patch']
message_count = 1.0
messages = ['356638']
nosy_count = 1.0
nosy_names = ['blueyed']
pr_nums = ['17159']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38806'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9']

[blueyed]

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 313a751 (Python 2.3), but it is not really clear.

I will create a PR reverting that part and see how it goes.