#26643: AlterModelManagers migration is generated for all Models with custom Managers pointing to the default Django Manager ---------------------------------+------------------------------------ Reporter: cybojenix | Owner: nobody Type: Bug | Status: new Component: Migrations | Version: master Severity: Release blocker | Resolution: Keywords: 1.10 | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 1 Easy pickings: 0 | UI/UX: 0 ---------------------------------+------------------------------------
Comment (by schinckel): Replying to [comment:8 schinckel]: > I believe reinstating the code at https://github.com/django/django/commit/ed0ff913c648b16c4471fc9a9441d1ee48cb5420 #diff-c8a3e1d248f8f5b10af7ac5b1d8479f4L516 is sufficient to fix this bug. Ah, not quite. This causes a deprecation warning in the manager inheritance stuff. Perhaps the check could be included in the autodetector, instead of the ModelState. -- Ticket URL: <https://code.djangoproject.com/ticket/26643#comment:9> 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/067.375188a4c69cdd8c7358bfa39ea4369a%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.