#26796: Add a check for limit_choices_to on ManyToManyField with an explicit
through model
-------------------------------------+-------------------------------------
Reporter: charettes | Owner:
Type: | kevswanberg
Cleanup/optimization | Status: assigned
Component: Core (System | Version: master
checks) |
Severity: Normal | Resolution:
Keywords: 1.11 | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"17a0a6667c3f77908f9427f6489e298c828133e2" 17a0a666]:
{{{
#!CommitTicketReference repository=""
revision="17a0a6667c3f77908f9427f6489e298c828133e2"
Refs #26796 -- Fixed ManyToManyField's limit_choices_to warning without a
through model.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26796#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.fd4714c0b4f708612f07546c1f01af61%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
