Python Internals · interview question
Which option describes the most likely pitfall around properties and descriptors?
Multiple choiceHardchapter-19-curatedpremiumpython-internalsproperties-and-descriptors
Answer and explanation
Correct answer
A. Treating properties as hidden business workflows can make simple reads unexpectedly expensive or stateful.
Why
Treating properties as hidden business workflows can make simple reads unexpectedly expensive or stateful. Calling out that risk matters because good answers mention explicit boundaries and surprise minimization.
Test yourself on Python Internals
A free test with instant, explained results. No account needed.
More Python Internals questions
- Which naming or modeling choice is strongest for import system and caching?
- What does a strong engineer do when reasoning through runtime patching code?
- A bug appears around reference counting and gc. What is the strongest first debugging move?
- Which explanation would best help the team align on closures and scope?
- When is closures and scope being used in the wrong way?
- What is the healthiest performance judgment around runtime patching?