Alex Waygood

If you tried to _use_ `Nested` in a type annotation anywhere without either quoting it or having `__future__` annotations enabled, it would fail, because the alias doesn't exist at runtime....

> We shouldn't do this in typeshed until PEP 692 is accepted. I think it's better to also wait in flake8-pyi. Yeah, I agree. Hopefully the PEP will be accepted,...

The PEP's been accepted now, but mypy's support is still guarded behind `--enable-incomplete-feature=Unpack` (our typeshed trackig issue is https://github.com/python/typeshed/issues/9710). We probably shouldn't write a lint encouraging it until it's properly...

Following #364, flake8-with-flake8-pyi-installed no longer emits errors for this code: ```py x: int y = x ``` That means we can now revisit this issue.

> I just saw [astral-sh/ruff#8818](https://github.com/astral-sh/ruff/issues/8818) and I've been wondering, should this apply to enums? Given they can be dynamically generated. Maybe that's not a use-case we'd want to support. I...

I'm a ruff maintainer now and I'm interested in this rule 😄 (but I can't speak for the rest of the ruff team)

> I can't see a good reason for selectively disabling only one of the two error codes. Yes, you're right -- it probably doesn't deserve its own error code. In...

> `None` is probably always a mistake IIRC from when I did the analysis a few months ago, there were still enough false positives even with just `Callable[, None]` that...

> We could check for this, but does it belong to this tool? This lint isn't really stub-specific. I'm starting to wonder if we should split the tool in two:...

> We could also try to get some of the non-pyi-specific checks accepted into flake8/pyflakes(?). We could try, but I think they would probably be rejected. I think the checks...