#28920: AlterModelManagers migration is generated for all Models with custom
Managers, which is not compatible with Django 1.8
----------------------------------+--------------------------------------
Reporter: Michał Bońkowski | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.11
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => invalid
Comment:
The behavior changed in c0cf73a57d7f77af348aeb854e7b4f670dc3cee7 which
suggests the new behavior is desired.
To keep your migrations compatible with older versions of Django, you must
[https://docs.djangoproject.com/en/stable/topics/migrations/#supporting-
multiple-django-versions generate them with the oldest version of Django
that you wish to support], so I see no problem there.
--
Ticket URL: <https://code.djangoproject.com/ticket/28920#comment:6>
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.e88f50a6de7b79f1a60ed35e6f43093e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
