Failure to parse f-strings when field has `=` at the end

[Ark-kun]

Fails when f-string field has = at the end:

f"aaaa {sys.version_info=} bbb"

  File "pasta/base/annotate.py", line 1537, in visit_FormattedValue
    self.attr(
  File "pasta/base/annotate.py", line 1864, in attr
    attr_parts.append(self.token(attr_val))
                      ^^^^^^^^^^^^^^^^^^^^
  File "pasta/base/annotate.py", line 1774, in token
    raise AnnotationError(
pasta.base.annotate.AnnotationError: Expected '!' but found '='
line 1: sys_version=} is inconsistent with {sys.version_info=}. "

https://docs.python.org/3/reference/lexical_analysis.html#formatted-string-literals

When the equal sign '=' is provided, the output will have the expression text, the '=' and the evaluated value. Spaces after the opening brace '{', within the expression and after the '=' are all retained in the output. By default, the '=' causes the repr() of the expression to be provided, unless there is a format specified. When a format is specified it defaults to the str() of the expression unless a conversion '!r' is declared.

Added in version 3.8: The equal sign '='.

[aryanyk]

Hi @Ark-kun @soupytwist

! I've been researching this issue and I have a fix in mind for the AnnotationError in visit_FormattedValue. I'd like to take this on. Could you please assign it to me? I will soon open an PR.

[aryanyk]

Hi @soupytwist @Ark-kun

I recently submitted a PR fixing Python 3.8+ f-string debug format parsing ({expr=}).

The issue was caused by an assumption in visit_FormattedValue that conversion
must always be introduced by '!', which is not true for debug f-strings.

The fix:

• Explicitly handles the debug specifier '='
• Keeps conversion parsing conditional
• Adds comprehensive tests

Tested on Python 3.10 and 3.11.
Python 3.12+ remains out of scope due to PEP 701.

Would love feedback on whether this aligns with the project’s direction.