#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 Kondou-ger):
Today I ran into this error again, while changing the `related_name` of a
M2M to self with `symmetrical=False`, and could finally create a project
that is able to reproduce this.
You can reproduce it by just running `./manage.py test`. Be minded though
that (about 50% now) sometimes the migration actually works and no
exception is thrown (probably caching related).
--
Ticket URL: <https://code.djangoproject.com/ticket/24513#comment:8>
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.b9b71e5e3aa408b699e0ac02d1ec5cbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
