[issue35355] Some Errors involving formatted strings aren't reported in the right place.

Terry J. Reedy added the comment: Evan, IDLE runs your code with the Python running IDLE. Bad tracebacks are created by Python and are usually, as in this case, the fault of Python. To decide, run your code directly with Python, at a command line, instead of indirectly with IDLE, and see

[issue35355] Some Errors involving formatted strings aren't reported in the right place.

Serhiy Storchaka added the comment: This looks like a duplicate of issue34364. -- nosy: +serhiy.storchaka resolution: -> duplicate superseder: -> problem with traceback for syntax error in f-string ___ Python tracker

[issue35355] Some Errors involving formatted strings aren't reported in the right place.

Change by Evan Newman : -- title: Some Errors involving formatted strings aren't reported in the right place. -> Some Errors involving formatted strings aren't reported in the right place. ___ Python tracker

[issue35355] Some Errors involving formatted strings aren't reported in the right place.

New submission from Evan Newman : Formatted strings seem to have some quirks. if you try putting in this, for example; print(f'{0 0}') ; you get a syntax error, which is probably intended, but where the error is reported is not always accurate. for example; #just a comment, it doesn't