#26643: AlterModelManagers migration is generated for all Models with custom
Managers pointing to the default Django Manager
---------------------------------+-------------------------------------
Reporter: cybojenix | Owner: schinckel
Type: Bug | Status: assigned
Component: Migrations | Version: master
Severity: Release blocker | Resolution:
Keywords: 1.10 | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Changes (by schinckel):
* owner: nobody => schinckel
* status: new => assigned
* needs_tests: 0 => 1
Comment:
Okay, I have a patch, but no tests:
https://github.com/schinckel/django/commit/38a0cb2a9bfb4752b661905a2de6278fed9771dd
Should I be creating a PR against 1.10.x, or master?
--
Ticket URL: <https://code.djangoproject.com/ticket/26643#comment:10>
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.95ee09bb3cf58642b6acd11dae378363%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
