#21794: No warning should be raised when defining an abstract model with no
app_label
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: aaugustin
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(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 |
-------------------------------------+-------------------------------------
Changes (by gregplaysguitar):
* status: closed => new
* resolution: fixed =>
Comment:
Hi, I'm going to reopen this because I'm pretty confident the issue is
still valid. At the moment I'm getting screeds of RemovedInDjango19
warnings and have no way to turn them off. It doesn't make sense for
abstract models to have an app_label, because by their very nature they
can be used in multiple apps.
--
Ticket URL: <https://code.djangoproject.com/ticket/21794#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 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.8e2f88d6bdaa4d44f68c7230da23d401%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
