Question
Which practice avoids a common mistake with Exceptions and Custom Errors?
- Ignore the Exceptions and Custom Errors issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Exceptions and Custom Errors problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Exceptions and Custom Errors that makes behavior less predictable as long as the code still runs.
- Do not swallow the original failure context with broad except blocks or vague replacement messages that destroy the debugging trail.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: D. Do not swallow the original failure context with broad except blocks or vague replacement messages that destroy the debugging trail.
Do not swallow the original failure context with broad except blocks or vague replacement messages that destroy the debugging trail. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python