Question
When should a Python developer choose weakref and Object Lifetime deliberately?
- Use weak references when a cache, lookup table, or observer relationship should not be the reason an object survives forever.
- Choose weakref and Object Lifetime mainly when you want to postpone validation and fix issues manually later.
- Choose weakref and Object Lifetime whenever you want the code to look more advanced, even if the design gets less clear.
- Choose weakref and Object Lifetime only to avoid modeling the real data shape or domain contract explicitly.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: A. Use weak references when a cache, lookup table, or observer relationship should not be the reason an object survives forever.
Use weak references when a cache, lookup table, or observer relationship should not be the reason an object survives forever. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python