Could you explain the use case for the code that needs to handle the different types of iterators?
On Friday, November 2, 2018 at 11:18:34 AM UTC-4, Dan Davis wrote: > > I'm wondering two things: > > - Is there any non-internals way to know what sort of iterable a > queryset is set to do? Should there be? Background - users should not > write code to look at isinstance(queryset._iterable_class, > FubarIterator) because that is a private interface (and it may be code > no longer in 2.x, since I'm currently looking at 1.11.x). > - Is looking at query.values_select, query.annotation_select, and > extra_select as is done by the ValuesIterable, ValuesListIterable, and > FlatValuesListItereable > a supported interface? Is there documentation for this? Should > there be? > > Thanks, > > -Dan > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9844cb0e-3137-4c47-8715-6910a721c348%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
