#22268: values_list() on a ManyToManyField returns extra None's when iterated
over.
-------------------------------------+-------------------------------------
Reporter: k_sze | Owner:
Type: Bug | anubhav9042
Component: Database layer | Status: assigned
(models, ORM) | Version: master
Severity: Normal | Resolution:
Keywords: orm, values_list, | Triage Stage: Accepted
ManyToManyField | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by erikr):
The examples in comment:15 and comment:16 do seem odd. However, have a
close look at #5768, where this behaviour seems to have been added. I
haven't read it in detail, but there may be some explanation in there of
the choices made.
--
Ticket URL: <https://code.djangoproject.com/ticket/22268#comment:20>
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.d8d2a854dc2a0ec49025557421dbd67c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
