Regression of false positive with e251 and type statement type variable defaults

[mikeshardmind]

ruff version 0.8.4
python version 3.13

prior issue: #13699 prior PR: #13704

src\salamander\_type_stuff.py:37:20: E251 [*] Unexpected spaces around keyword / parameter equals
   |
37 | type Coro[T: object = Any] = Coroutine[None, None, T]
   |                    ^ E251
   |
   = help: Remove whitespace

src\salamander\_type_stuff.py:37:22: E251 [*] Unexpected spaces around keyword / parameter equals
   |
37 | type Coro[T: object = Any] = Coroutine[None, None, T]
   |                      ^ E251
   |
   = help: Remove whitespace

These are false positives.

Applying the fix leads to (correctly) identifying:

src\salamander\_type_stuff.py:37:20: E225 [*] Missing whitespace around operator
   |
37 | type Coro[T: object=Any] = Coroutine[None, None, T]
   |                    ^ E225
   |
   = help: Add missing whitespace

config is here if useful

[InSyncWithFoo]

I think the E225 error is also a false positive. The equal sign in this case is not an operator, same as the one for value parameter defaults (playground):

def _[T: int=bool](): ...
#           ^ E252 (correct), E225 (incorrect)
def _(t: int=True): ...
#           ^ E252 (correct)

[Garrett-R]

Here's a minimal working example of the original bug: playground.

I'll try to submit a PR for this one.

[InSyncWithFoo]

@Garrett-R I was already working on a fix, and I just submitted it since I didn't know you was working on one too (I read your comment via the mails, and GitHub doesn't notify users about edits...). I'm sorry; hope you don't mind.

[Garrett-R]

No prob! Actually hadn't started, still getting acquainted with Rust / Ruff and getting IDE nicely set up. 😎