Re: Defining apps.py name while upgrading from Django 2.X to 3.X

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 Djan

Defining apps.py name while upgrading from Django 2.X to 3.X

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* *

Re: Makemigrations/migrate in existing database

``` python manage.py makemigrations python manage.py migrate --fake ``` On Friday, June 4, 2021 at 7:21:03 PM UTC+5:30 Mahendra Yadav wrote: > I think surely run makemigrations and migrate > > Mahendra Yadav > > On Fri, 4 Jun 2021, 18:28 Ankita Sharma, wrote: > >> Hello Team >> Hope all are

Resolution for #32503

I am waiting for this https://code.djangoproject.com/ticket/32503 this ticket to get resolved. For me it is standing as a blocker for upgrading from 2.2 to 3.2.x as my project has many JSON and Textfields. I expected it to be included in 3.2.4. Just want to know in which version this patch can