You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
File and lineno is not reported for syntax error in f-string #81246
bpo-34364: problem with traceback for syntax error in f-string
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=<Date2019-05-27.17:48:33.640>created_at=<Date2019-05-27.15:11:54.021>labels= ['interpreter-core', '3.8', 'type-bug', '3.7']
title='File and lineno is not reported for syntax error in f-string'updated_at=<Date2019-05-27.17:48:33.639>user='https://github.com/ods'
I'm pretty sure there's already an issue for this, but I don't have time to search for it now.
This is not an easy problem to solve. I've been working on it on and off for almost a year. I'll eventually get to it, but the changes are pretty invasive.
Activity
ods commentedon May 27, 2019
Minimal example to reproduce:
Here we see in track trace "<fstring>" and line number in erroneous expression in f-string, but no "f_bug.py" and line number in it.
ericvsmith commentedon May 27, 2019
I'm pretty sure there's already an issue for this, but I don't have time to search for it now.
This is not an easy problem to solve. I've been working on it on and off for almost a year. I'll eventually get to it, but the changes are pretty invasive.
tirkarthi commentedon May 27, 2019
Related open issue : bpo-34364. Also bpo-29051 which was closed as duplicate of bpo-34364.