#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
-------------------------------------+-------------------------------------
Changes (by Ana Paula Gomes):
* status: assigned => new
* owner: Ana Paula Gomes => (none)
Comment:
This ticket requires more knowledge about the codebase (which I don't have
yet). But I would suggest using exceptions like AlreadyRegistered and
NotRegistered in AdminSite.
For those interested in taking a look at places implementing registers,
here a list of some classes:
- Library: template/library
- Apps: apps/registry.py
- CheckRegistry: core/checks/registry.py
- AdminSite: contrib/admin/sites.py
--
Ticket URL: <https://code.djangoproject.com/ticket/29443#comment:9>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.fac7dd7a3e8a61c09d6d9b1297202ada%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
