#29443: Unify registries in Django
-------------------------------------+-------------------------------------
Reporter: Johannes Hoppe | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Utilities | Version: master
Severity: Normal | Resolution:
Keywords: plugin, registry, | Triage Stage: Accepted
pattern, utils |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
I took a look to the Django own registry implementations, and struggled to
find much code that could be factorized in a common class. The structure
of the registries themselves are various: list, set, mapping, sometimes
several of them. Then the implementations differ much depending on the
internal registry structure.
Johannes, could you explore that a bit and show us some example of current
code that would benefit from a utility class?
--
Ticket URL: <https://code.djangoproject.com/ticket/29443#comment:10>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.4538a8c8dcbcd2f052cc4a9cbd9ece51%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
