#27362: Omitting default_app_config in __init__.py happens too easily.
-------------------------------------+-------------------------------------
Reporter: Thomas Güttler | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: 1.10
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aymeric Augustin):
Historically this ticket would have been kept open in the "design decision
needed" stage. We started closing tickets with no clear way forwards a
couple years ago to keep open tickets actionable.
I believe that the documentation is clear is it stands and (unfortunately)
not a good solution here because a programmer debugging such a problem is
unlikely to be perusing the documentation of apps.
Perhaps we could add a check to raise a warning if there's an AppConfig
subclass defined in an `apps` submodule -- the conventional location? That
seems quite prone to false positives...
Other arguments or ideas welcome...
--
Ticket URL: <https://code.djangoproject.com/ticket/27362#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 [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.e9cea81c80ac57cf26e66e30e8422750%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
