Repository navigation
problem with traceback for syntax error in f-string #78545
Description
| BPO | 34364 |
|---|---|
| Nosy | @ods, @ericvsmith, @serhiy-storchaka, @MojoVampire |
| PRs | lineno and col_offset for multi-line string tokens. #10021 |
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 = 'https://github.com/ericvsmith'
closed_at = <Date 2020-11-19.12:39:34.592>
created_at = <Date 2018-08-08.20:42:15.759>
labels = ['interpreter-core', '3.8', 'type-bug', '3.7']
title = 'problem with traceback for syntax error in f-string'
updated_at = <Date 2020-11-19.12:39:34.592>
user = 'https://bugs.python.org/bgailer'bugs.python.org fields:
activity = <Date 2020-11-19.12:39:34.592>
actor = 'iritkatriel'
assignee = 'eric.smith'
closed = True
closed_date = <Date 2020-11-19.12:39:34.592>
closer = 'iritkatriel'
components = ['Interpreter Core']
creation = <Date 2018-08-08.20:42:15.759>
creator = 'bgailer'
dependencies = []
files = []
hgrepos = []
issue_num = 34364
keywords = ['patch']
message_count = 6.0
messages = ['323301', '323309', '323311', '326264', '326268', '326269']
nosy_count = 5.0
nosy_names = ['ods', 'eric.smith', 'bgailer', 'serhiy.storchaka', 'josh.r']
pr_nums = ['10021']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34364'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
Activity
bgailer commentedon Aug 8, 2018
Inconsistent tracebacks. Note that the traceback for bug.py does not
reference the
module file and line number.
MojoVampire commentedon Aug 9, 2018
So the bug is that the line number and module are incorrect for the f-string, right? Nothing else?
ericvsmith commentedon Aug 9, 2018
I think this is a duplicate, but I can't find the exact issue. I don't think it's exactly the same as bpo-29051.
ericvsmith commentedon Sep 24, 2018
I worked on this at the core sprint, and I have a patch almost ready.
serhiy-storchaka commentedon Sep 24, 2018
Great! I was going to take it. Will be glad to make a review.
ericvsmith commentedon Sep 24, 2018
It's more elaborate than I'd like, but I think it's the right way to solve it: I'm passing in the starting line and column number to the parser machinery.