#21794: No warning should be raised when defining an abstract model with no
app_label
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database | Keywords: app-loading
layer (models, ORM) | Has patch: 1
Severity: Normal | Needs tests: 0
Triage Stage: | Easy pickings: 1
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Since those models are never registered and meant to be used by different
apps it doesn't make much sense to raise a warning in this case.
I think this case was just overlooked when Aymeric refactored app-loading.
Attaching a patch fixing the issue and removing an extra space between
`in` and `INSTALLED_APPS` in the warning message.
--
Ticket URL: <https://code.djangoproject.com/ticket/21794>
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/052.f3d900eb2690d921523c074d9f3d6c4b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
