OK - why borrow trouble. There is plenty to do just maintaining current
interfaces, and adding major features - like the new db functions in 2+.
On Saturday, November 3, 2018 at 7:36:00 PM UTC-4, Adam Johnson wrote:
>
> I have code in my package Django-MySQL that uses the internals of
> queryset
I have code in my package Django-MySQL that uses the internals of
querysets. It’s not so bad to maintain with enough test coverage and
ensuring it keeps up to date with the latest Django. The fact the interface
is private means that it could change at any time, but practically that
doesn’t mean oft
I was thinking of providing a package containing a couple of DRF renderers
that work directly from querysets. DRF Serializers are great when you
need to render a hierarchical structure, and/or when you expect to parse a
POST body containing the structure. For returning non-hierarchical
resul
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?
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
