Brent Westbrook 92ecfc908b [syntax-errors] Make async-comprehension-in-sync-comprehension more specific (#17460) ... ## Summary While adding semantic error support to red-knot, I noticed duplicate diagnostics for code like this: ```py # error: [invalid-syntax] "cannot use an asynchronous comprehension outside of an asynchronous function on Python 3.9 (syntax was added in 3.11)" # error: [invalid-syntax] "`asynchronous comprehension` outside of an asynchronous function" [reveal_type(x) async for x in AsyncIterable()] ``` Beyond the duplication, the first error message doesn't make much sense because this syntax is _not_ allowed on Python 3.11 either. To fix this, this PR renames the `async-comprehension-outside-async-function` semantic syntax error to `async-comprehension-in-sync-comprehension` and fixes the rule to avoid applying outside of sync comprehensions at all. ## Test Plan New linter test demonstrating the false positive. The mdtests from my red-knot PR also reflect this change.		2025-04-24 15:45:54 -04:00
..
resources	[pyupgrade] Preserve parenthesis when fixing native literals containing newlines (UP018) (#17220)	2025-04-24 08:48:02 +02:00
src	[syntax-errors] Make async-comprehension-in-sync-comprehension more specific (#17460)	2025-04-24 15:45:54 -04:00
Cargo.toml	Bump 0.11.7 (#17613)	2025-04-24 13:06:38 -05:00