Python Internals · interview question
Which option describes the most likely pitfall around import system and caching?
Multiple choiceHardchapter-19-curatedpremiumpython-internalsimport-system-and-caching
Answer and explanation
Correct answer
C. Treating imports as free and contextless makes certain runtime bugs harder to untangle.
Why
Treating imports as free and contextless makes certain runtime bugs harder to untangle. Calling out that risk matters because candidates who can explain sys.modules and import caching usually sound well-grounded.
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?