Why makemigrations create an auto_date_time migration in dynamic_scraper app?

[Umair Ashraf]

Related: https://github.com/holgerd77/django-dynamic-scraper/issues/74

I am running python manage.py makemigrations and it is generating a migration in dynamic_scraper app with the name like 0026_auto_20190924_1710.py. I don't know why that is necessary?

[Umair Ashraf]

Following the guide at https://django-dynamic-scraper.readthedocs.io/en/0.13-dev/getting_started.html

I have created https://github.com/umrashrf/django-address-manager

Because of lines here https://github.com/umrashrf/django-address-manager/blob/master/address_manager/models.py#L16-L17 and here https://github.com/umrashrf/django-address-manager/blob/master/address_manager/models.py#L33-L34

`python manage.py makemigrations` is creating a new migration inside dynamic_scraper app named 0026_auto_20190924_1813.py (the timestamp keep changing based on when makemigrations was run). This is not good because during deployment there won't be makemigrations and there won't exist that intermediate migration 0026_auto_20190924_1813.py. I know django would create such intermediate migration for proxy models but I don't think this is a proxy model, is it?

[Umair Ashraf]

It's a bug in django-dynamic-scraper.