#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
---------------------------------+--------------------------------------
Comment (by kaedroho):
I've so far been unable to reproduce this issue. It looks like it's
failing when running that AlterField operation on the "groups" field.
Could you paste the code for the user model before this migration so we
can see what this operation is changing?
--
Ticket URL: <https://code.djangoproject.com/ticket/24513#comment:3>
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.144cb2626db3c06872e6e3bd3fcd7027%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
