Python Internals · interview question
What is the clearest sign that code around import system and caching should be refactored?
Multiple choiceHardchapter-19-curatedpremiumpython-internalsimport-system-and-caching
Answer and explanation
Correct answer
B. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Understand module loading and caching well enough to explain circular-import pain and startup shape.
Test yourself on Python Internals
A free test with instant, explained results. No account needed.
More Python Internals questions
- Which naming or modeling choice is strongest for import system and caching?
- What does a strong engineer do when reasoning through runtime patching code?
- A bug appears around reference counting and gc. What is the strongest first debugging move?
- Which explanation would best help the team align on closures and scope?
- When is closures and scope being used in the wrong way?
- What is the healthiest performance judgment around runtime patching?