Python Internals · interview question
What is the clearest sign that code around reference counting and gc should be refactored?
Multiple choiceHardchapter-19-curatedpremiumpython-internalsreference-counting-and-gc
Answer and explanation
Correct answer
A. 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. Know the basics of reference counting and garbage collection so object retention problems stop feeling mysterious.
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?