#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: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Suor):
Are there any real world scenario for using numerous thrown out dynamic
classes? And while they are thrown out they still live long enough to use
signals. Probably the right approach here will be just ignore this case.
About inherited signals. I agree that they could simplify some code
(making it more implicit by the way). It will also make signals
implementation slower and more complex. It seems that somebody should
start another ticket or topic on django-developers to resolve this
question. Who knows? Maybe a lot of people want this?
About implementation. It appears to me that my approach is cleaner when
sender inheritance is not involved, otherwise one should just go with
caching. So this solution should be delayed until we get any decision on
previous question.
--
Ticket URL: <https://code.djangoproject.com/ticket/16679#comment:13>
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.
