Python Internals · interview question
Which move is the best default when import system and caching become part of this workflow?
Multiple choiceHardchapter-19-curatedpremiumpython-internalsimport-system-and-caching
Answer and explanation
Correct answer
B. Understand module loading and caching well enough to explain circular-import pain and startup shape.
Why
Understand module loading and caching well enough to explain circular-import pain and startup shape. That is the stronger engineering move because candidates who can explain sys.modules and import caching usually sound well-grounded. Treating imports as free and contextless makes certain runtime bugs harder to untangle.
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?