Python Internals · interview question

What is the healthiest performance judgment around closures and scope?

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

python

def build_multiplier(factor: int):
    def apply(value: int) -> int:
        return value * factor
    return apply

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 closures and scope.Keep closures and scope implicit so the script stays short and hope the next engineer infers the rule.Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.

Answer and explanation

Correct answer

D. Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.

Why

Premature optimization is usually weaker than targeted optimization backed by measurement.

Test yourself on Python Internals

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

Start free test

All Python Internals questions →

What is the healthiest performance judgment around closures and scope?

Correct answer

Why

More Python Internals questions