Question
Which practice avoids a common mistake with Variables, References, and Mutability?
- Ignore the Variables, References, and Mutability issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Variables, References, and Mutability problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Variables, References, and Mutability that makes behavior less predictable as long as the code still runs.
- Do not confuse rebinding a name with mutating a shared object, because the two actions produce different downstream behavior.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: D. Do not confuse rebinding a name with mutating a shared object, because the two actions produce different downstream behavior.
Do not confuse rebinding a name with mutating a shared object, because the two actions produce different downstream behavior. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python