#29443: Unify registries in Django
-------------------------------------+-------------------------------------
Reporter: Johannes Hoppe | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Utilities | Version: master
Severity: Normal | Resolution: wontfix
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
-------------------------------------+-------------------------------------
Changes (by Claude Paroz):
* status: new => closed
* resolution: => wontfix
Comment:
At first sight, I don't see a compelling reason to refactor the various
registry implementations, as they serve different purposes.
I'll close the ticket, but if someone comes later with some POC code that
demonstrates advantages to unify registry implementations, we'll happily
reconsider that decision.
--
Ticket URL: <https://code.djangoproject.com/ticket/29443#comment:12>
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.23917a22578e62639988e95bb78bbf55%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
