#23961: makemigrations doesn't create migrations package when app_label isn't
specified
----------------------------+------------------------------------
Reporter: dibrovsd | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: migration | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by carljm):
I thought that until support for apps without migrations was removed, it
was intentional that `makemigrations` would only create the migrations
module if you gave it an app-label (I think that's the behavior with or
without `MIGRATION_MODULES` set). Otherwise it would be very difficult to
use migrated apps alongside unmigrated apps in the same project. I think
the plan is in Django 1.9 (when support for unmigrated apps goes away),
makemigrations should start always creating the migration module.
I'm not entirely sure about that, but that was my understanding. If that's
the case, there still may be a documentation update needed.
--
Ticket URL: <https://code.djangoproject.com/ticket/23961#comment:2>
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.ce44b57961d99071912b3a8748baa40b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
