Alex Waygood

> @colesbury What is the canonical name for this feature, "no-gil python", "gil disabled" or "free-threaded python"? Not Sam, but as per the Steering Council decision, the canonical name is...

> [ ] 3.11 Variadic generics These did involve the introduction of some new syntax: unpacking using `*` at the outermost level of an expression in a type annotation was...

I support detecting these syntax errors via the linter (Option (2)) wherever possible. I think it'll be great to have these errors be `# noqa`-able and to be able to...

The only reasons I can see for wanting to suppress a syntax error diagnostic are: - Deliberate syntax errors (e.g. in test files or data files) - A bug in...

Thanks, I agree that ruff's behaviour is incorrect here. For other readers who may not be familiar — this is an experimental syntax for "inline TypedDicts" that has been floated...

> Perhaps @AlexWaygood can elucidate whether or not this should trigger for functions with `yield`. > > [peps.python.org/pep-0525](https://peps.python.org/pep-0525) may be helpful. Yeah, async functions that contain `yield` are async generators...

> Yeah, async functions that contain `yield` are async generators that can be used in `async for` loops by other async functions. So I don't think ruff should emit this...

Thanks for the idea! I'm not _sure_ I see the benefit of prohibiting all `type: ignore` comments, though, since presumably you'd easily be able to switch the "never use a...

> The linter rule is designed to prevent you from footgunning yourself, so to speak, and it's up to your judgement if you want to override that; if you're really...

Guessing this is due to [the recent change to UP031](https://github.com/astral-sh/ruff/pull/11019)? Cc. @plredmond