Python Internals · interview question

If reference counting and gc fails in production, what handling philosophy is strongest?

Multiple choiceHardchapter-19-curatedpremiumpython-internalsreference-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.Solve the symptom with comments only and avoid changing the code shape around reference counting and gc.Fail in a way that preserves the reason, keeps the boundary honest, and avoids hiding the real source of the problem.

Answer and explanation

Correct answer

D. Fail in a way that preserves the reason, keeps the boundary honest, and avoids hiding the real source of the problem.

Why

Reliable systems preserve context. Silent failure makes the next debugging round slower and riskier.

Test yourself on Python Internals

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

Start free test

All Python Internals questions →

If reference counting and gc fails in production, what handling philosophy is strongest?

Correct answer

Why

More Python Internals questions