#24513: "... has no field named None" with M2MField when migrating
---------------------------------+------------------------------------
Reporter: Kondou-ger | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8rc1
Severity: Normal | Resolution:
Keywords: migrations, bug | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by patrys):
Side note:
Tracing the cause of this became much easier after I've changed
`_get_m2m_attr()` end with a `raise AttributeError()`. There does not seem
to be a case when it silently returning `None` in case of a missing
attribute match is deliberate and expected.
--
Ticket URL: <https://code.djangoproject.com/ticket/24513#comment:11>
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/068.5f45b875ed1e44ba539ab1e67fcf0d46%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
