wrong line number for f-string syntax errors

[sam-s]

Bug description

When there is a syntax error in the code called from an f-string, pylint issues an uninformative message with a wrong line number.
This happens with pylint 2.15.8 but not with 2.15.6.
However, the problem is probably with the older Python.

"https://github.com/PyCQA/pylint/issues/7914"
# the error is in the next line
print(f"{f(x}}")

Command used

pylint a.py

Pylint output

************* Module a
a.py:1: [E0001(syntax-error), ] Parsing failed: 'invalid syntax (<fstring>, line 1)'

Expected behavior

************* Module a
a.py:3: [E0001(syntax-error), ] Parsing failed: 'f-string: closing parenthesis '}' does not match opening parenthesis '(' (<unknown>, line 3)'

Pylint version

• good output:

pylint 2.15.6
astroid 2.12.13
Python 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0]

• bad output:

pylint 2.15.8
astroid 2.12.13
Python 3.7.15 (default, Oct 31 2022, 22:44:31) 
[GCC 7.3.1 20180712 (Red Hat 7.3.1-15)]

OS / Environment

both linux

[Pierre-Sassoulas]

This is something we do not control, the ast module got better in cpython for python 3.8 and above. Closing as there's nothing we can reasonably do.