#24563: Migration for M2M Field fails with FieldDoesNotExist when removing null=True from model -------------------------------------+------------------------------------- Reporter: GitRon | Owner: nobody Type: Bug | Status: new Component: Migrations | Version: 1.8 Severity: Normal | Resolution: Keywords: migrations, | Triage Stage: many2many, nullable | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by codefisher): The 1.8.0 release as given by pip. I guess this is a dup then. Did not find the other ones when I did a search for it. -- Ticket URL: <https://code.djangoproject.com/ticket/24563#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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/064.c46192021c24ba73d5db65917038e487%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.