Python Internals · interview question

Another engineer will maintain this code later. What choice helps the most around closures and scope?

Multiple choiceMediumchapter-19-curatedpremiumpython-internalsclosures-and-scope

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.Solve the symptom with comments only and avoid changing the code shape around closures and scope.Keep closures and scope implicit so the script stays short and hope the next engineer infers the rule.

Answer and explanation

Correct answer

B. 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. Candidates who explain scope clearly usually sound much more senior.

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 closures and scope?

Correct answer

Why

More Python Internals questions