[issue31140] Insufficient error message with incorrect formated string literal

2022-03-28 Thread Peter Lovett
Peter Lovett added the comment: Thanks Eric. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31140] Insufficient error message with incorrect formated string literal

2022-03-28 Thread Eric V. Smith
Eric V. Smith added the comment: Yes, they should update Python. A lot of work went in to fixing these issues, and won't be backported. -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue31140] Insufficient error message with incorrect formated string literal

2022-03-28 Thread Peter Lovett
Peter Lovett added the comment: I'm not getting the problem on 3.9.7 on Windows. Did get it on 3.7 (3.7.11?) on a different Windows machine last week. Not getting the problem on 3.10.4 The wrong line number is a problem for IDLE's syntax highlighter, that marks the first line as a Syntax

[issue31140] Insufficient error message with incorrect formated string literal

2022-03-28 Thread Peter Lovett
Change by Peter Lovett : -- nosy: +PeterL777 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31140] Insufficient error message with incorrect formated string literal

2019-12-14 Thread Philip Rowlands
Philip Rowlands added the comment: Status as of 3.9.0a1: == test.py above appears fixed, i.e. reasonable error message. $ ./python test.py File "/home/bob/pybug/Python-3.9.0a1/test.py", line 2 hello = f"{world)}" ^ SyntaxError: f-string: unmatched ')' ==

[issue31140] Insufficient error message with incorrect formated string literal

2018-01-10 Thread Christoph Zwerschke
Christoph Zwerschke added the comment: I can confirm that the problem still exists in Python 3.6.4 and 3.7.0a4. Here is another way to demonstrate it: Create the following file test.py: # test hello = f"{world)}" Note that there is a syntax error in the f-string in

[issue31140] Insufficient error message with incorrect formated string literal

2017-09-06 Thread Łukasz Langa
Changes by Łukasz Langa : -- pull_requests: +3396 ___ Python tracker ___ ___

[issue31140] Insufficient error message with incorrect formated string literal

2017-09-04 Thread Eric V. Smith
Changes by Eric V. Smith : -- versions: +Python 3.7 ___ Python tracker ___ ___

[issue31140] Insufficient error message with incorrect formated string literal

2017-09-04 Thread Eric V. Smith
Changes by Eric V. Smith : -- stage: -> needs patch ___ Python tracker ___ ___

[issue31140] Insufficient error message with incorrect formated string literal

2017-08-08 Thread Eric V. Smith
Eric V. Smith added the comment: Thanks. There was some work on this recently: I'll try and check 3.7 later today. -- ___ Python tracker ___

[issue31140] Insufficient error message with incorrect formated string literal

2017-08-08 Thread chris.259263
chris.259263 added the comment: Hi Eric, running the script from the terminal on my system (macOS, Python 3.6.2) gives the same ErrorMessage as you stated. The problem is the output "line 1". Running the script from IDLE (3.6.2), the error points to the first line. And in IDLE you do not

[issue31140] Insufficient error message with incorrect formated string literal

2017-08-08 Thread Eric V. Smith
Eric V. Smith added the comment: On 3.6.1 on Windows, I get: % python3 bpo-31140.py File "", line 1 (a>2s) ^ SyntaxError: invalid syntax Which is far from ideal, but at least points to (a portion of) the correct text. I won't have access to a copy of 3.6.2 or 3.7 until later

[issue31140] Insufficient error message with incorrect formated string literal

2017-08-08 Thread chris.259263
New submission from chris.259263: Trying to run a script with a bug in a formated string literal (in the example the ":" is missing) throws an "invalid syntax" error at the first expression of the script. Example: import math a = "a" b = f"{a>2s}" # forgotten ":", should be f"{a:>2s}"