You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would recommend to wait for this a bit as we could change the AST representation for an implicit string concatenation node which then would make this easier to solve.
## Summary
It seems like the range of an `ExprStringLiteral` can be somewhat
unreliable when the string is part of an implicit concatenation with an
f-string. Using the tokens themselves is more reliable.
Closes#8680.
Closes#7784.
Note that this is unrelated to the new f-string changes.
If a unicode string is implicitly concatenated with a f-string, then the fix removes the first character of the string instead of the prefix:
The fix:
This is because the "foo" string is part of the outer f-string expression and the range of the string constant is within the quotes.
The text was updated successfully, but these errors were encountered: