#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 |
-------------------------------------+-------------------------------------
Changes (by Aymeric Augustin <aymeric.augustin@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"2f65b8e14c03a6b43c11d5de791b8d4d91721777"]:
{{{
#!CommitTicketReference repository=""
revision="2f65b8e14c03a6b43c11d5de791b8d4d91721777"
Fixed #21794 -- Adjusted warning for abstract models.
As far as I can tell, they don't need an app_label.
Thanks Simon Charette for the report and the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21794#comment:5>
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.1952288ab5957ef165ad0c17c7ee5ab7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
