Python Internals · interview question

Another engineer will maintain this code later. What choice helps the most around reference counting and gc?

Multiple choiceHardchapter-19-curatedpremiumpython-internalsreference-counting-and-gc

Solve the symptom with comments only and avoid changing the code shape around reference counting and gc.Keep reference counting and gc implicit so the script stays short and hope the next engineer infers the rule.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Make the rule obvious in names, flow, and boundaries so the next reader does not have to reverse-engineer your intent.

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 like this topic because it connects language knowledge to operational reasoning.

Test yourself on Python Internals

A free test with instant, explained results. No account needed.

Start free test

All Python Internals questions →

Another engineer will maintain this code later. What choice helps the most around reference counting and gc?

Correct answer

Why

More Python Internals questions