#16547 closed New feature (wontfix)
Add support for signal priority.
Reported by: | EvilX | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | yes | Needs documentation: | yes |
Needs tests: | yes | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Sometimes is very important to call one signal earlier of all other or call signals in queue.
Currently, when you connect signals, them executed in order of connect; but its non trivial to guaratee order of connect method execution.
Proposed solution is to add order argument to connect signal, so when you need, you can supply correct ordering, but all other code still compatible.
Attached patch provide this feature.
Attachments (1)
Change History (4)
by , 13 years ago
Attachment: | signal.patch added |
---|
comment:1 by , 13 years ago
Component: | Uncategorized → Core (Other) |
---|---|
Needs documentation: | set |
Needs tests: | set |
Triage Stage: | Unreviewed → Design decision needed |
comment:2 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:3 by , 13 years ago
Hi jacob,
I think the signal framework is a really powerful tool for building reusable applications, and when you're sticking together multiple reusable applications one of the common issues could be the order of signal execution.
Django's signal framework is deliberately minimalistic. It's a pattern that doesn't really match the rest of Django, and we try to minimize its use. As such, I don't believe we should be adding features -- even good ones like this. If people need a robust signal-handling system, they should look elsewhere.
Thanks!