Question
Which practice avoids a common mistake with Classes and Dataclasses?
- Ignore the Classes and Dataclasses issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Classes and Dataclasses problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Classes and Dataclasses that makes behavior less predictable as long as the code still runs.
- Do not create classes that are only glorified dictionaries if the behavior, invariant, and contract are still unclear.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: D. Do not create classes that are only glorified dictionaries if the behavior, invariant, and contract are still unclear.
Do not create classes that are only glorified dictionaries if the behavior, invariant, and contract are still unclear. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python