#22485: makemigrations fails with dependencies to unmigrated apps
-------------------------------------+-------------------------------------
Reporter: apollo13 | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Release blocker | Resolution:
Keywords: migrations, | Triage Stage: Accepted
unmigrated, makemigrations | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by andrewgodwin):
Running makemigrations for the apps isn't enough to get them in there
early enough - contenttypes in particular loads too early in the Django
process that it can't be migrated (I tried to add migrations to contrib
apps and failed due to things like that and the tests).
I have a plan for fixing this, which just means fixing the projectstate
creator to always include unmigrated apps when it's making migration
states. There's no need for fake migrations, hopefully, and the
autodetector shouldn't need any changes.
--
Ticket URL: <https://code.djangoproject.com/ticket/22485#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.eb062e85260f48d2854cade6f3ddd5c8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
