Moderate Signals Question 111 of 228

How do weak references affect Django signal receivers?

Python & Django · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: DJANGO MVT

URLRoute request

ViewBusiness logic

Model + TemplateData + HTML

Simple meaning

By default Django stores receivers as weak references, so a local function can be garbage-collected and silently stop running.

WHY — Signals instead of guessing?

Why interviewers care about Signals:

This is a process

question about Signals.

Panels listen for order,

trade-offs, and what you would actually do on a Python project - not buzzwords.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

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:

1
By default Django stores
receivers as weak references, so a local function can be garbage-collected and silently stop running.
2
Use weak=False or connect
a module-level function so the handler stays alive.
3
This is a frequent
cause of 'it worked in the shell once' bugs.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“Use weak=False or connect a module-level function so the handler stays alive.”

Break into beats

UseweakFalseorconnecta

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

By default Django stores receivers as weak references, so a local function can be garbage-collected and silently stop running. Use weak=False or connect a module-level function so the handler stays alive.