Inheritance
Mixins
Reusable functionality through multiple inheritance
Interview: Design patterns — tests understanding of mixin best practices, naming conventions, and cooperative inheritance
Mixins are small, focused classes designed to add specific functionality to other classes through multiple inheritance. Unlike regular base classes, mixins are not meant to stand alone — they provide reusable behavior that can be "mixed in" to any class. They're one of the safest and most practical uses of multiple inheritance.
Mixin Design Principles
- Single responsibility: Each mixin adds one specific capability
- No __init__ or minimal __init__: Mixins should work with any class
- Use super(): Always call super() to support cooperative inheritance
- Naming convention: Name classes with "Mixin" suffix (e.g.,
JsonMixin) - No dependencies: Mixins should be self-contained and not depend on specific base classes
Common Mixin Patterns
- Serialization (JSON, XML, CSV output)
- Logging and debugging
- Authentication/authorization checks
- Caching and memoization
- Comparison operators (ComparableMixin)
Interview Tip
Django extensively uses mixins: LoginRequiredMixin, PermissionRequiredMixin, CreateView, etc. Be ready to explain how mixin ordering affects behavior (leftmost = highest priority).
Use Cases
Adding serialization capabilities (JSON, XML, CSV) to any model
Authentication/authorization checks (LoginRequiredMixin)
Logging and audit trails for any class
Caching behavior for data access layers
Adding comparison operators to data classes
Common Mistakes
Creating mixins that depend on specific base class methods (coupling)
Not using super() in mixin methods — breaks cooperative inheritance
Adding too much logic to a single mixin (violates single responsibility)
Wrong mixin ordering in class definition (leftmost has highest priority)
Not naming mixins with the "Mixin" suffix (unclear intent)