Python way and interfaces

Question

Python

Python does not natively support interfaces. All the discussions I found referred to "duck typing". But, for example, if I have a set of classes that, when iterating, I need to distinguish between the actions they support, which are not very dependent on the base class, then in the case of interfaces, I can check that the class implements, say, the ILoggable interface, then I will make sure that the class has all the necessary methods. But in the case of duck typing, you will either have to check each necessary method, or make some kind of wrapper that will actually do the same thing as the interface. What does the ideology of python say about this? Since there are no interfaces, it means that they somehow manage without them (I don’t take third-party implementations into account).

Answer 1

From the Python glossary
Abstract base classes complement duck-typing by providing a way to define interfaces when other techniques like hasattr() would be clumsy or subtly wrong (for example with magic methods). ABCs introduce virtual subclasses, which are classes that don't inherit from a class but are still recognized by isinstance() and issubclass(); see the abc module documentation. Python comes with many built-in ABCs for data structures (in the collections module), numbers (in the numbers module), and streams (in the io module). You can create your own ABCs with the abc module.
Apparently, this is what is needed.
From myself, I’ll say that I don’t notice a strong passion for ABC in the community (and in general for checking interfaces) - they are more likely for the standard library.

Answer 2

Why not try to make the interface part a separate class, run it into multiple inheritance and check its occurrence in bases? Your interface will be like a mixin.

Answer 3

docs.zope.org/zope.interface