#25830: Unnecessary migrations with Python3
----------------------------+--------------------
Reporter: bronger | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------
With Python3, "manage.py makemigrations" may under certain circumstances
never be satisfied and always wants to create new migrations.
Steps to reproduce:
{{{
git clone https://github.com/juliabase/juliabase.git
cd juliabase
python3 manage.py makemigrations institute
python3 manage.py makemigrations institute
python3 manage.py makemigrations institute
...
}}}
Every time "makemigrations" is called, a new migration file is created.
Apparently, Django+Python3 does not recognise that the Meta options of the
latest migration and the current model classes are equivalent.
--
Ticket URL: <https://code.djangoproject.com/ticket/25830>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.e7eca35c788ce8ffdd91977a64c9c7e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
