#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 Mariusz Felisiak):
Replying to [comment:6 Manel Clos]:
> Ok, but take into account that this has worked on every Django version
til 3.2, and there is no indication about what's wrong or deprecated, it
just stops working because of the automatic AppConfig discovery. Now I've
to create a different app just to put some *global* templates, sigh...
Yes but it was only by chance, that kind of configuration wasn't
officially supported.
> Now I've to create a different app just to put some *global* templates,
sigh...
You don't need to have an app for global templates.
--
Ticket URL: <https://code.djangoproject.com/ticket/32692#comment:8>
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.39952152ffa3d1aa228621f9d6329747%40djangoproject.com.
