Also want to know if this change is backward compatible? As far as I have implemented and tested, this AppConfig name changed worked fine with both 2.2 and 3.2, please mention this too while answering.
On Wednesday, June 9, 2021 at 2:23:10 AM UTC+5:30 Omkar D wrote: > > In my Django 2.X project, I had the following structure generated by > default: > > *project_name* > * ---> animal_app* > * ---> apps.py* > * name = "animal"* > * ---> zebra* > * ---> apps.py* > * name = "zebra"* > > Note that zebra is *sub-app* of animal app, and name is attribute of it's > app config. > > Now, after upgrading to 3.X, I figured out that I needed to change* > name="zebra"* to *name="animal.zebra"* > > I wanted to understand why this change is needed and what does it mean? > From the docs and release note it is not much clearly stated for the > sub-apps. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f6995b58-5d90-4016-8888-67f445812fd3n%40googlegroups.com.
