Python Internals · interview question
Another engineer will maintain this code later. What choice helps the most around mutability traps?
Multiple choiceMediumchapter-19-curatedpremiumpython-internalsmutability-traps
Answer and explanation
Correct answer
D. Make the rule obvious in names, flow, and boundaries so the next reader does not have to reverse-engineer your intent.
Why
Maintainability comes from explicit intent. Interviewers often use this topic because it reveals whether you truly understand Python's evaluation rules.
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?