When would you use a metaclass instead of a class decorator or __init_subclass__?
Prefer init_subclass or decorators; reach for a metaclass only for inheritance-wide or deep control
The PEP 487 guidance is clear: init_subclass should cover most cases where you previously needed a metaclass, because it is a normal classmethod hook that runs on every subclass. Class decorators are even simpler and apply to a single class. Metaclasses remain the right choice when you need to control the class namespace before the class object exists, customize prepare, interact with the metaclass itself (for example subclassing ABCMeta), or affect every class in a hierarchy in a way that must be part of type identity. If you find yourself writing a metaclass only to register subclasses or validate methods, you are probably over-engineering.
- 1
init_subclass: best for per-subclass validation, registration, and hooking into class creation without changing type identity.
- 2
Class decorator: best for a single class transformation, easy to apply and remove, plays well with type checkers.
- 3
Metaclass: best when you must customize the class namespace via prepare, or when your feature must be part of the class's type.
- 4
Trade-off: metaclasses compose poorly. Combining two metaclasses requires a shared subclass, which is intrusive for library consumers.
- 5
Common mistake: using a metaclass for singleton, registry, or attribute validation, all of which init_subclass or descriptors handle more cleanly.
- 6
Version note: init_subclass and set_name were added in 3.6 precisely to reduce metaclass usage. PEP 487 documents the intent.
Scenario Questions
0-2 years experience
- 1You want every subclass to register itself. Which mechanism do you choose?
- 2What does a class decorator receive and what does it return?
2-5 years experience
- 1You need to reject subclasses that fail to define a required method. Metaclass or __init_subclass__?
- 2You need to apply a transformation to a single class only. Which tool is simplest?
5-8 years experience
- 1You are writing a public library and your metaclass conflicts with ABCMeta. How do you redesign the API?
- 2You need custom class namespace behavior like ordered attributes. Which hook is required?
8+ years experience
- 1Design a plugin framework that is compatible with ABCMeta, dataclasses, and user-provided base classes, avoiding metaclass conflicts.
- 2Compare the cost of metaclass-based validation versus __init_subclass__ and decorators on class creation time, inheritance behavior, and tooling compatibility.
Follow-up Questions
- What does __prepare__ let a metaclass do that __init_subclass__ cannot?
- How do class decorators interact with static type checkers compared to metaclasses?