#22268: values_list() on a ManyToManyField returns extra None's when iterated
over.
-------------------------------------+-------------------------------------
Reporter: k_sze | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: orm, values_list, | Needs documentation: 0
ManyToManyField | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by erikr):
Changing this to not include the None value is definitely backwards
compatibility breaking. So far, in this ticket, we have not been able to
reach a clear consensus on what the correct behaviour is. To me, the
current behaviour does not seem unreasonable. The issue raised in
comment:7 is valid, but I don't see how removing extra None's would help -
this is simply not the right query for that question.
Given that there is no strong case for removing the None's, I think we
should not break backwards compatibility, and therefore keep the existing
behaviour. If you disagree, please make sure to clarify exactly how you
would like the behaviour to change. Otherwise, I do think a documentation
patch would be good.
--
Ticket URL: <https://code.djangoproject.com/ticket/22268#comment:11>
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/063.42738a3bf37a75db1097e4c960792d05%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
