What is surprising about m2m_changed?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
It fires with actions such as pre_add, post_add, pre_remove, and post_clear, and pk_set may be None on clear.
WHY — Signals instead of guessing?
Why interviewers care about Signals:
who only read docs from people who shipped.
and tied to Python work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1It fires with actions
such as pre_add, post_add, pre_remove, and post_clear, and pk_set may be None on clear.
- 2It can fire twice
depending on which side of the relation you update.
- 3Receivers must be idempotent
and should not assume both sides' caches are warm.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
It fires with actions such as pre_add, post_add, pre_remove, and post_clear, and pk_set may be None on clear. It can fire twice depending on which side of the relation you update.