Question
Which practice avoids a common mistake with Comprehensions?
- Ignore the Comprehensions issue and rely on team discipline instead of clearer APIs or invariants.
- Do not compress multi-step business rules into one comprehension when named intermediate values would make the rule safer to explain.
- Silence the Comprehensions problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Comprehensions 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 compress multi-step business rules into one comprehension when named intermediate values would make the rule safer to explain.
Do not compress multi-step business rules into one comprehension when named intermediate values would make the rule safer to explain. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python