Python Internals · interview question
Which boundary choice best fits runtime patching in a maintainable Python system?
Multiple choiceHardchapter-19-curatedpremiumpython-internalsruntime-patching
Answer and explanation
Correct answer
B. Keep the concern close to the data or API boundary that owns it instead of scattering it across unrelated helpers.
Why
Responsibility should follow ownership. When the concern lives near the right boundary, the system is easier to test and explain.
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?