Python Internals · interview question
A teammate submits shaky reference counting and gc code. Which review comment is the strongest?
Multiple choiceHardchapter-19-curatedpremiumpython-internalsreference-counting-and-gc
Answer and explanation
Correct answer
A. Make the rule clearer and easier to explain. Know the basics of reference counting and garbage collection so object retention problems stop feeling mysterious.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. Assuming the runtime will eventually solve every memory problem can hide real lifecycle design mistakes.
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?