Question
Which practice avoids a common mistake with Tuples and Fixed Records?
- Ignore the Tuples and Fixed Records issue and rely on team discipline instead of clearer APIs or invariants.
- Do not rely on long anonymous tuples when readers cannot remember what each position means.
- Silence the Tuples and Fixed Records problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Tuples and Fixed Records that makes behavior less predictable as long as the code still runs.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: B. Do not rely on long anonymous tuples when readers cannot remember what each position means.
Do not rely on long anonymous tuples when readers cannot remember what each position means. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python