#27362: Omitting default_app_config in __init__.py happens to easily.
--------------------------------+--------------------------------------
Reporter: Thomas Güttler | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Changes (by Aymeric Augustin):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Yes, I can see the problem.
That's one of the reasons why I'm against `default_app_config`. It's only
there for backwards compatibility and should only be used by pluggable
apps that predate Django 1.7, need a custom app config and don't want to
ask their users to update their `INSTALLED_APPS` setting.
Unfortunately, even if `default_app_config` was removed, we'd still be
stuck with two kinds of apps: those that provide a custom AppConfig and
those that don't. This results in a mixed style in `INSTALLED_APPS`, and
then it's easy to reference an app by its package name and load it with
the base `AppConfig` class instead of its custom `MyAppConfig` class.
Like you I'm not really coming up with great ideas to improve the
situation...
--
Ticket URL: <https://code.djangoproject.com/ticket/27362#comment:1>
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/065.f103feb7f70227488520d11fa72b585f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
