Question
Which practice avoids a common mistake with String Formatting and f-Strings?
- Ignore the String Formatting and f-Strings issue and rely on team discipline instead of clearer APIs or invariants.
- Do not cram complex business logic into the interpolation expression when intermediate named values would improve readability.
- Silence the String Formatting and f-Strings problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of String Formatting and f-Strings 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 cram complex business logic into the interpolation expression when intermediate named values would improve readability.
Do not cram complex business logic into the interpolation expression when intermediate named values would improve readability. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python