-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support typing.Protocol #135
Comments
I'm not sure how I feel about protocols where the implementers don't have to say what interfaces they support. It matches duck typing, but it is hard for tools that want to go find implementations (IDEs, a registry, etc.) Still, in some mythical future zope.interface, sitting atop that machinery would indeed give (2) above, which is a big win for those buying into mypy or PyCharm. |
That said, PEP 544 (under rejected ideas) does say interfaces are conceptually a superset of protocols. So your point stands. |
PEP-0544 introduce
typing.Protocol
which allows defining an interface that can be validated on runtime.This is currently available via a non-official extension to the
typing
module called typing-extensions.Although it seems similar to zope functionality, it is very different:
Can zope utilize the already existing validation implementation to also validate Protocols on runtime.
This will allow a developer to write an interface once (via a Protocol) that could be checked statically using the existing Protocol implementation and also dynamically using zope's implementation.
See more information on this StackOverflow thread: https://stackoverflow.com/questions/43830996/verify-that-an-unknown-module-object-is-obliged-to-a-specific-interface-python/55131689
The text was updated successfully, but these errors were encountered: