Repository navigation
Wrong traceback for AssertionError while running under pdb #79586
Description
| BPO | 35405 |
|---|---|
| Nosy | @serhiy-storchaka, @tirkarthi |
| Superseder |
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 = <Date 2018-12-04.16:32:14.269>
created_at = <Date 2018-12-04.10:17:13.643>
labels = ['3.7', '3.8', 'type-bug', 'library']
title = 'Wrong traceback for AssertionError while running under pdb'
updated_at = <Date 2018-12-04.16:32:14.268>
user = 'https://github.com/tirkarthi'bugs.python.org fields:
activity = <Date 2018-12-04.16:32:14.268>
actor = 'xtreak'
assignee = 'none'
closed = True
closed_date = <Date 2018-12-04.16:32:14.269>
closer = 'xtreak'
components = ['Library (Lib)']
creation = <Date 2018-12-04.10:17:13.643>
creator = 'xtreak'
dependencies = []
files = []
hgrepos = []
issue_num = 35405
keywords = []
message_count = 4.0
messages = ['331025', '331033', '331045', '331063']
nosy_count = 2.0
nosy_names = ['serhiy.storchaka', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '16482'
type = 'behavior'
url = 'https://bugs.python.org/issue35405'
versions = ['Python 2.7', 'Python 3.6', 'Python 3.7', 'Python 3.8']
Activity
tirkarthi commentedon Dec 4, 2018
While running under pdb when I have an assertion error after the command continue then the assertion error is mentioned with the statement under which I have executed continue command in pdb. Below script has an assertion error on assert 1 == 2 but when I execute continue from assert 1 == 1 then it shows the line assert 1 == 1 with the AssertionError. I first noticed this with unittest but seems to be a general issue with assert. This is confusing while debugging unittest failures.
I searched for issues but couldn't find a related one and this exists on master and 2.7. I assume this is a case where AssertionError doesn't use the current line and uses the one where pdb is executed with continue? I don't know if this is an issue with pdb or assert so I am adding Library as the component.
# Reproducible script
assert 1 == 1
assert 1 == 2
# Executing on master
serhiy-storchaka commentedon Dec 4, 2018
There is nothing specific for assert and AssertionError. Other example:
tirkarthi commentedon Dec 4, 2018
Thanks Serhiy, is this a known behavior or issue since it's from 2.7 ? This is highly confusing and misleading as in your example and also while debugging tests that fail at a different line of assertion statement from the current line in pdb which might also be a different assert statement.
tirkarthi commentedon Dec 4, 2018
Seems this is a known issue and has an open PR #6233 . I checked out the PR locally and it works fine on the examples presented though has merge conflicts with master. I am closing it as duplicate of bpo-16482 that links to other possible issues.