Python Internals · interview question

Which option describes the most likely pitfall 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.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Assuming the runtime will eventually solve every memory problem can hide real lifecycle design mistakes.Keep reference counting and gc implicit so the script stays short and hope the next engineer infers the rule.

Answer and explanation

Correct answer

C. Assuming the runtime will eventually solve every memory problem can hide real lifecycle design mistakes.

Why

Assuming the runtime will eventually solve every memory problem can hide real lifecycle design mistakes. Calling out that risk matters because 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 →

Which option describes the most likely pitfall around reference counting and gc?

Correct answer

Why

More Python Internals questions