#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: 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 gregplaysguitar):
Loic said
> Should this message be a little more explicit about what's necessary to
fix this deprecation warning?
> Usually this kind of message implies that if you manually do what the
future version of Django will
> do automatically, then you'll get rid of the deprecation warning, but
obviously setting app_label to
> None has no effect.
My point is that ther isn't anything that can be done to fix this
deprecation warning, so personally I think the
original patch – which removes it – does address Loic's concerns, and
should be fast-tracked
into a release.
At the moment I'm just ignoring all warnings because most of them are
related to this (and hence can't be fixed.)
--
Ticket URL: <https://code.djangoproject.com/ticket/21794#comment:15>
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.6c0224c0876284f343ccaa191a4d12cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
