#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 carljm):
Even though there is a behavior change here (from setting `app_label` to
something probably-bogus, to setting it to `None`), it is a change that
quite likely won't affect anybody. And I don't think we should raise
pending-deprecation warnings that don't have a straightforward update path
to get rid of them.
I would say this is like any other minor backwards-incompatible change to
a semi-internal detail (which is arguably a bugfix anyway, as the
currently-set value is bogus): we should just do it (that is, leave
`app_label` as `None` for abstract models that aren't in an installed app
and don't have it set explicitly), note it in the release notes, and be
done.
--
Ticket URL: <https://code.djangoproject.com/ticket/21794#comment:16>
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.0e389ff4a508dde8167b9855e01b5be7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
