#23599: Default application used in startapp has an empty migration package
-------------------------------------+-------------------------------------
     Reporter:  yakky                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Migrations           |                  Version:  1.7
     Severity:  Normal               |               Resolution:
     Keywords:  migrations,          |             Triage Stage:  Accepted
  dependencies, template             |      Needs documentation:  0
  application                        |  Patch needs improvement:  0
    Has patch:  0                    |                    UI/UX:  0
  Needs tests:  0                    |
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by andrewgodwin):

 Well, the bug mentioned above is definitely not to do with the empty
 migrations folder (which, as was correctly posted, is so new apps are not
 ignored by makemigrations - we can remove the empty folder when we
 deprecate the syncdb-style path in 2.0, as at that point makemigrations
 can assume everything has migrations).

 The root of the cause here seems to be the custom user model, which as the
 docs mention in several places, must be made in the first migration of an
 app. ``makemigrations`` is meant to have code that ignores this style of
 error while it's running (as you may be doing it to make the migration for
 said user model), but I've not seen that result in this error before -
 usually it manifested as a graph dependency error (as the migration
 depending on the custom user model would have a dependency on an app with
 no migrations).

 I'm not sure what the Django bug is here - the original reporter or people
 more familiar with CMS will need to dig down and either give a simple
 project that can reproduce the issue (i.e. one without the intricacies of
 CMS) or work out why it's trying to import PageUser when, as far as the
 CMS bug says, it's someone's own personal custom user.

--
Ticket URL: <https://code.djangoproject.com/ticket/23599#comment:6>
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/063.d1fc64c028d07903bf480b42ed9659aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to