#23471: makemigrations fails if you take out a function used in a previous
migration
-------------------------------+--------------------
Reporter: danielsamuels | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
In a previous migration I was using a method to determine the default
value for a model field, that code was then changed and the method
removed, but I am no longer able to use `makemigrations` because it tries
to call that method. The same thing happens if you were using a custom
model field and then change to a different one and remove the old code. To
get around this, you either have to modify the migration files manually,
or keep the old code in until you have at least run a makemigrations, not
sure if you have to keep it indefinitely.
--
Ticket URL: <https://code.djangoproject.com/ticket/23471>
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/056.979d268eaa74d8e7c30a2d7b3847d040%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
