#16547: Add support for signal priority.
-------------------------------------+-------------------------------------
Reporter: EvilX | Owner: nobody
Type: New | Status: closed
feature | Component: Core (Other)
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: wontfix | Has patch: 1
Triage Stage: Design | Needs tests: 1
decision needed | Easy pickings: 0
Needs documentation: 1 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by jacob):
* status: new => closed
* resolution: => wontfix
Comment:
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!
--
Ticket URL: <https://code.djangoproject.com/ticket/16547#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
