Python Internals · interview question
A bug appears around reference counting and gc. What is the strongest first debugging move?
Multiple choiceHardchapter-19-curatedpremiumpython-internalsreference-counting-and-gc
import gc
print(gc.get_threshold())Answer and explanation
Correct answer
B. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.
Why
That approach is reliable because it creates evidence. 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?
- 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?
- If reference counting and gc fails in production, what handling philosophy is strongest?