#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):
> Based on the tested workaround in the description, what about this?
https://github.com/manelclos/django/commit/c5da1ff59d6d53dc25cf503be9d59c1f825fb10a
This change is not correct, you can still use `apps.py` unless you do this
in the main project and you don't use your project as an app, because it
will discover two configs. I think proposed change makes it even more
confusing.
--
Ticket URL: <https://code.djangoproject.com/ticket/32692#comment:11>
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.40d89cb852983f8cd1978defa5bd927c%40djangoproject.com.
