Python Internals · interview question
Which option treats reference counting and gc as an engineering policy decision instead of a syntax trick?
Multiple choiceHardchapter-19-curatedpremiumpython-internalsreference-counting-and-gc
Answer and explanation
Correct answer
D. Use it to make the operational rule explicit, observable, and maintainable under real workload conditions.
Why
Senior answers focus on ownership, reliability, and maintainability rather than only API recall.
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?