Question
Which practice avoids a common mistake with Modules, Packages, and Imports?
- Ignore the Modules, Packages, and Imports issue and rely on team discipline instead of clearer APIs or invariants.
- Do not fix poor boundaries by scattering imports inside functions unless you are solving one specific cycle or startup constraint deliberately.
- Silence the Modules, Packages, and Imports problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Modules, Packages, and Imports 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 fix poor boundaries by scattering imports inside functions unless you are solving one specific cycle or startup constraint deliberately.
Do not fix poor boundaries by scattering imports inside functions unless you are solving one specific cycle or startup constraint deliberately. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python