This is a problem with mypy's dataclasses plugin, I suppose. However, as mypy would have already processed the class (I think?) before the plugin gets to it, I'm not certain it can be fixed. I suppose the workaround would be to # type: ignore the necessary lines and run mypy with --warn-unused-ignores (you can stick this in a config file too) to tell you when you can remove the # type: ignore, ie because mypy gains support.

Thanks. I'll implement the suggest workaround.

I also get "MyClass" has no attribute "prop" [attr-defined] in mypy for any reference of that attribute -- the workaround suggested doesn't address these.

e.g.

from dataclasses import dataclass, InitVar


@dataclass
class Baz:
    foo: InitVar[int]

    @property  # type: ignore
    def foo(self) -> int:
        return 0


print(Baz(0).foo)

results in error: "Baz" has no attribute "foo" [attr-defined]

Maybe if TypeInfo would start having a separate dict for annotations rather than put it all into names. Might be a bit of a refactor though, which could be less painful if TypeInfo.names becomes a "wrapper" around two maps, one with annotations and the other with identifiers.