Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#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


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)

signal.patch (2.8 KB ) - added by EvilX 13 years ago.

Download all attachments as: .zip

Change History (4)

by EvilX, 13 years ago

Attachment: signal.patch added

comment:1 by Matthias Kestenholz, 13 years ago

Component: UncategorizedCore (Other)
Needs documentation: set
Needs tests: set
Triage Stage: UnreviewedDesign decision needed

comment:2 by Jacob, 13 years ago

Resolution: wontfix
Status: newclosed

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.


comment:3 by anonymous, 12 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.

Note: See TracTickets for help on using tickets.
Back to Top