Bug report
When parsing multiline f-strings, e.g.
the ast has the wrong column information for test. Here's the diff between 3.9.12 (lhs, gets it wrong) and 3.9.1 (gets it right).
FormattedValue( FormattedValue(
value=Name( value=Name(
id='test', id='test',
ctx=Load(), ctx=Load(),
lineno=2, lineno=2,
col_offset=11, | col_offset=7,
end_lineno=2, end_lineno=2,
end_col_offset=15), | end_col_offset=11),
Your environment
Tested on a variety of python versions (on linux); 3.9.1 gets it right, it's wrong in 3.9.2 and has the same wrong value all the way to 3.9.12. The offset seems related to the start column of the opening triple quotes. I went through previous f-string parsing bugs but this does not look like a duplicate of any of them.
Bug report
When parsing multiline f-strings, e.g.
the ast has the wrong column information for
test. Here's the diff between 3.9.12 (lhs, gets it wrong) and 3.9.1 (gets it right).Your environment
Tested on a variety of python versions (on linux); 3.9.1 gets it right, it's wrong in 3.9.2 and has the same wrong value all the way to 3.9.12. The offset seems related to the start column of the opening triple quotes. I went through previous f-string parsing bugs but this does not look like a duplicate of any of them.