#22371: AttributeError during replaying/loading of migration: 'module' object
has
no attribute 'RemovedModel'
---------------------------------+--------------------------------------
Reporter: blueyed | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7-beta-1
Severity: Release blocker | Resolution:
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 loic84):
* severity: Normal => Release blocker
Comment:
I'm not completely convinced this is needed, `TaggableManager` could
provide a `deconstruct` method and handle serializing `Model` objects.
That said if models as arguments are common enough we could support them
out of the box.
I don't think a documentation fix is warranted, we already document what
types are supported by the serializer.
I'd let Andrew decide if we should go with the proposed fix or wontfix the
ticket, it's just a matter of making a decision so bumping the ticket to
Release Blocker.
--
Ticket URL: <https://code.djangoproject.com/ticket/22371#comment:5>
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.83692d30e8c700da5cc1b0a0a688722d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.