#22371: AttributeError during replaying/loading of migration: 'module' object
has
no attribute 'RemovedModel'
---------------------------------+--------------------------------------
Reporter: blueyed | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7-beta-1
Severity: Release blocker | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by andrewgodwin):
* status: new => closed
* resolution: => wontfix
Comment:
Yep, I'm WONTFIXing this. Taggable needs to return those as strings and do
the lookups in the app registry itself (if it doesn't already); migrations
won't freeze model references, down that path madness lies.
Note for taggable people: The apps registry you want to use is the one on
the model, i.e. `model._meta.apps` - that way model versioning will work
correctly.
--
Ticket URL: <https://code.djangoproject.com/ticket/22371#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/065.6ecb6229dff12512cd4541662f66634c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
