Add configuration option to enable strict enforcement of typing.override (PEP 698)

[NeilGirdhar]

Will Pyright be implementing the strict enforcement of typing.override described in PEP 698?

[erictraut]

I've added a new optional diagnostic check called reportImplicitOverride. It's off by default even in strict mode. When enabled, it implements strict enforcement of PEP 698.

One open question that's not addressed in PEP 698 is whether __init__ and __new__ should be exempt from this check. For now, I've opted to not exempt these methods, but I could be convinced that they should be exempted since they are exempt from LSP checks.

[NeilGirdhar]

I've added a new optional diagnostic check called reportImplicitOverride.

Oh, my mistake! Somehow, I missed this when I checked the documentation. (Edit: Oh, I see you just added it to the docs 😄. Perfect, thanks!)

but I could be convinced that they should be exempted since they are exempt from LSP checks.

I share the same logic. If you don't exempt them, users will have to always mark them as @override, which doesn't seem that helpful?

[erictraut]

I'll close the issue once the next version of pyright is published.

[NeilGirdhar]

Okay, sorry, and thanks again!

[erictraut]

This is included in pyright 1.1.300, which I just published. It will also be included in a future release of pylance.