#12288: Validate that values in INSTALLED_APPS are unique
-------------------------------------+-------------------------------------
Reporter: Piotr Czachur | Owner: susan
<zimnyx@…> | Status: closed
Type: | Version: master
Cleanup/optimization | Resolution: fixed
Component: Core (Other) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: sprint200912 | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by mjtamlyn):
Also worth noting that this patch does not actually prevent the issue
discussed - you can just as easily create a `User` model with an
`app_label` of `auth`, and have just as much of a problem. Can we not
apply this validation at the app cache level if this is what we're trying
to avoid? The first patch is good as it catches easy mistakes, the second
seems overkill. I'm not sure it's a pattern we should encourage, perhaps
print a warning on server start, but I think it should be allowed.
--
Ticket URL: <https://code.djangoproject.com/ticket/12288#comment:34>
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/090.4294725bdf73b3a53f6ea07c821640cd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
