#16679: Speed up signals by caching the reveicers per sender
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.3
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Suor):
Yes, my solution is not suitable for inherited signals. And once we have
those it should be discarded. But do we really need them? Implementing as
little as possible is generally a good idea.
And, about dynamic creation of model subclasses, I do pretty much of it.
And in my experience, signals are usually connected in
.contribute_to_class() call which is done for every new model class, thus
no need for inherited signals here.
--
Ticket URL: <https://code.djangoproject.com/ticket/16679#comment:8>
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.
