Retuning an instance of the class being defined which provides an interface is not handled about mypy-zope HOT 6 OPEN

Super happy to be getting real typing via mypy-zope, by the way. It's great. And thanks for the quick replies to these tickets.

Thanks! I'm glad mypy exists and it was possible to marry zope with it. Interfaces become so much more meaningful with it! :)

from mypy-zope.

I think the actual issue is that @provider isn't handled, unlike @implementer.

from mypy-zope.

Yes, mypy-zope doesn't know anything about @provider. That said, I think your declaration is not quite correct? If instance of RequestURL implements IDependencyInjector, as registerInjector suggests, shouldn't RequestURL be declared with @implementer instead?

from mypy-zope.

Heh… I had to ask @glyph about this also. @implementer says that instances of the class will provide the interface. @provider says that the class itself does so. (Note that the methods are all class methods.)

from mypy-zope.

Super happy to be getting real typing via mypy-zope, by the way. It's great. And thanks for the quick replies to these tickets.

from mypy-zope.

Heh… I had to ask @glyph about this also. @implementer says that instances of the class will provide the interface. @provider says that the class itself does so. (Note that the methods are all class methods.)

Right, but registerInjector returns an instance of RequestURL. So, in order for registerInjector return type to be correct, an instance of RequestURL must provide the IDependencyInjector . However, it does not provide that interface. Only the class itself does, according to @provider declaration.

So, even though @provider is currently not supported by mypy-zope, I suspect the type hint on registerInjector is not entirely correct. I'd say registerInjector has to return cls, not cls(). Or, alterntively, RequestURL must implement IDependencyInjector, not provide it.

from mypy-zope.