#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 Johannes Hoppe):
Hi Claude,
yes you are absolutely right. Ana and I discovered the same problem during
the springs at DjangoConEu'18.
The implementations are extremely different. Maybe a good reason to
refactor it, maybe a good reason to just leave it be.
It's definitely a very difficult tasks. Kudos to whomever solves this ;)
Best
-Joe
--
Ticket URL: <https://code.djangoproject.com/ticket/29443#comment:11>
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.6edc6a5fd43db72b2a253e7a26014c21%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
