#22965: InvalidBasesError for unmigrated apps subclassing contrib
---------------------------------+-------------------------------------
     Reporter:  CollinAnderson   |                    Owner:  nobody
         Type:  Bug              |                   Status:  closed
    Component:  Migrations       |                  Version:  1.7-rc-1
     Severity:  Release blocker  |               Resolution:  duplicate
     Keywords:                   |             Triage Stage:  Accepted
    Has patch:  0                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
---------------------------------+-------------------------------------
Changes (by andrewgodwin):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Yep, closing this in favour of #22922; this error is probably most caused
 by unmigrated depending on migrated.

 Collin: If we had migrated run before syncdb, then migrated apps couldn't
 depend on unmigrated apps, which is much more untenable (think about all
 the unmigrated apps in the wild; most new apps are going to be migrated,
 so this way round works best). To detect dependencies we'd need to give
 them migrations (due to the way syncdb handles circular foreign keys) and
 tada, the problem has gone away anyway.

 I wish we could solve this problem but I've looked into it a lot and we
 can't. The reason the language is "it's not advised" is because you can
 depend with foreign keys and suchlike fine; it's importing a base class
 that really blows stuff up. We should at least mention that by name, and
 probably call out auth specifically in the release notes as it's now
 migrated.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22965#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/072.0bdca37120a6947b30f07b35fc9142ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to