#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:  Accepted
     Severity:  Normal               |      Needs documentation:  0
     Keywords:  app-loading          |  Patch needs improvement:  0
    Has patch:  1                    |                    UI/UX:  0
  Needs tests:  0                    |
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by Carl Meyer <carl@…>):

 In [changeset:"ac359dc7710ed8c62b6f058fe5a0ecfd6ce27602"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ac359dc7710ed8c62b6f058fe5a0ecfd6ce27602"
 [1.7.x] Fixed #21794 -- Removed deprecation warning for abstract models
 outside an app.

 Backport of e7b9a58b081299b30f807d5c66f7a5d1940efe4c from master.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/21794#comment:19>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f36eba060eb2fb9ffb11250dbfdec143%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to