[issue31140] Insufficient error message with incorrect formated string literal

[Peter Lovett]

Peter Lovett  added the comment:

Thanks Eric.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[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 Error, even if that line is a comment. 

This is an issue for ArcGIS Pro users, which is (I think) currently shipping 
with Python 3.7.11, so those users may come across it. Best solution would be 
for Esri to update their Python version to something newer.
https://support.esri.com/en/technical-article/13224

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[Peter Lovett]

Change by Peter Lovett :


--
nosy: +PeterL777

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[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 ')'


==
bpo-31140.py is not as bad a initially reported, but still gives the wrong line 
number.

$ ./python bpo-31140.py
  File "", line 1
(a>2s)
^
SyntaxError: invalid syntax


===
And my own example which led me to this bug. The syntax error is on line 3, not 
line 1.

$ cat fruit.py
pass
pass
s = f"{My favourite fruit is {apple}}"

$ ./python -V
Python 3.9.0a1

$ ./python fruit.py
  File "", line 1
(My favourite fruit is {apple})
^
SyntaxError: invalid syntax

--
nosy: +philiprowlands
versions: +Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[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 line 2 which has a closing 
parentheses, but no opening one.

Import this from Python 3.6.4 or 3.7.0a4:

>>> import test
Traceback (most recent call last):
  File "", line 1, in 
  File "", line 1
(world))
   ^
SyntaxError: unexpected EOF while parsing

The problem here is that the error message does not contain the name of the 
erroneous file (test.py), points to a wrong line (line 1 instead of line 2), 
and also shows parentheses instead of braces around the word "world", which are 
not there in the original code. This can make it hard to locate such errors.

Note that when there are other kinds of errors in the f-string, or other kinds 
of "unexpected EOF" in the imported file, the errorenous file is usually 
reported correctly in the error message. Only certain kinds of syntax errors in 
f-strings seem to be problematic.

--
nosy: +cito

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[Łukasz Langa]

Changes by Łukasz Langa :


--
pull_requests: +3396

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[Eric V. Smith]

Changes by Eric V. Smith :


--
versions: +Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[Eric V. Smith]

Changes by Eric V. Smith :


--
stage:  -> needs patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[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 get the useful hint "(a>2s)" but just "SyntaxError: invalid 
syntax".

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[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 today. Can you show 
the exact output from 3.6.2?

--
components: +Interpreter Core
nosy: +eric.smith

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31140] Insufficient error message with incorrect formated string literal

[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}"

Running this script throws an "invalid syntax" error in the first line "import 
math".

In a large program this behavior makes it nearly impossible to find the real 
bug in the program as the error message does not give any hint about the line 
or the type of the error in the program.

Using Python 3.6.2, IDLE 3.6.2 on Mac macOS Sierra (10.12.1)

--
messages: 299901
nosy: chris.259263
priority: normal
severity: normal
status: open
title: Insufficient error message with incorrect formated string literal
type: behavior
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com