#24513: "... has no field named None" with M2MField when migrating
---------------------------------+--------------------------------------
Reporter: Kondou-ger | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.8rc1
Severity: Normal | Resolution:
Keywords: migrations, bug | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Can you to backtrack the exception and try to figure out why the
`get_field(None)` call is happening?
{{{
File "/home/kondou/testenv/lib/python3.4/site-
packages/django/db/models/options.py", line 552, in get_field
return self.fields_map[field_name]
KeyError: None
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24513#comment:1>
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.e9719b0da0bd5cdbd03d992a8d0c92bf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
