#21794: No warning should be raised when defining an abstract model with no
app_label
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: aaugustin
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Database layer | Resolution: fixed
(models, ORM) | Triage Stage: Ready for
Severity: Normal | checkin
Keywords: app-loading | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by gregplaysguitar):
I'm getting this warning when inheriting from an abstract base class in
Django 1.7, but if I set {{{app_label = None}}} in my abstract base class,
it causes another error, because all the model classes inheriting from it
now think they are in an app labelled {{{None}}}. Does this mean that as
of Django 1.9 *all* model classes will need to have {{{app_label}}}
explicitly set? If not I don't think there should be any warning for an
abstract base class in this case, because there's no solution.
I may have misunderstood something here, so please feel free to set me
straight!
--
Ticket URL: <https://code.djangoproject.com/ticket/21794#comment:8>
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.c8afc35def3693e226bb9b1292e468f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
