What problem does the diamond inheritance pattern cause, and how does Python's MRO resolve it?
Diamond inheritance duplicates ancestors; C3 MRO linearizes so each class appears once
The diamond problem appears when two classes inherit from a common base and a fourth class inherits from both. In languages without a clear rule, the base can be initialized or overridden twice, causing duplicated state or ambiguous method dispatch. Python solves this statically: C3 linearization produces a single order that includes each ancestor exactly once, and preserves the relative order of bases. So in class D(B, C) where B and C both derive from A, the MRO is D, B, C, A, object. With cooperative super() calls, init and other methods run exactly once per class in the chain.
- 1
The diamond is not inherently a bug; it becomes a bug when base classes are not written cooperatively.
- 2
Cooperative pattern: each init calls super().init(**kwargs) and pops only the arguments it consumes.
- 3
Trade-off: cooperative super() keeps the chain consistent but makes signatures harder to read and breaks naive direct calls.
- 4
Common mistake: calling BaseClass.init(self) explicitly, which bypasses the MRO and can run a class twice or skip one entirely.
- 5
Common mistake: assuming the leftmost base wins for every attribute. The MRO decides, and it may put a right-side class before a shared ancestor.
- 6
Version note: the diamond behavior described is C3 linearization from Python 2.3 onward and is uniform across Python 3.
Scenario Questions
0-2 years experience
- 1Two parent classes both define greet. Which one runs for the child class?
- 2What is the MRO of D when class D(B, C) and both B and C inherit from A?
2-5 years experience
- 1You call Parent.__init__(self) directly in a diamond hierarchy and one class runs twice. How do you fix it with super()?
- 2A mixin defines an attribute also defined by a sibling mixin. How do you reason about which wins?
5-8 years experience
- 1You add a logging mixin into a deep hierarchy and logs appear twice. How do you diagnose and fix the super() chain?
- 2You are designing a plugin hierarchy where multiple base plugins define hooks. How do you ensure each hook runs exactly once?
8+ years experience
- 1Design a cooperative mixin framework where every class accepts **kwargs and validates required parameters, without breaking on unexpected keys.
- 2Explain how C3 linearization interacts with metaclass conflicts and how to resolve a metaclass MRO clash in a real framework.
Follow-up Questions
- What goes wrong if one class in the diamond does not call super().__init__?
- How would you make cooperative multiple inheritance work with required positional arguments?