#32692: Django 3.2 automatic AppConfig discovery breaks projects working in
3.1.8
-------------------------------+--------------------------------------
Reporter: Manel Clos | Owner: nobody
Type: Bug | Status: closed
Component: contrib.admin | Version: 3.2
Severity: Normal | Resolution: invalid
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 Manel Clos):
Hi Marius, just checked the documentation:
https://docs.djangoproject.com/en/3.2/ref/applications/#projects-and-
applications
The project package is often extended to include things like fixtures,
CSS, and templates which aren’t tied to a particular application.
There’s no restriction that a project package can’t also be considered
an application and have models, etc. (which would require adding it to
INSTALLED_APPS).
I really think Django 3.2 is breaking this, but I can open a different
ticket to fix the documentation if you prefer that.
--
Ticket URL: <https://code.djangoproject.com/ticket/32692#comment:7>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.4e8af66943a244bfe32d6c9da0cd61da%40djangoproject.com.
