I just ran into the same issue several people before me have: Paginator is a bit dangerous when handed a queryset, and QuerySetPaginator should be used instead.
This ticket exists, but no core dev has contributed to discussion yet. http://code.djangoproject.com/ticket/7478 I'd like to avoid making it dangerously easy to consume memory/cpu on the full queryset. isinstance(object_list, QuerySet) is a fairly straightforward way to collapse Paginator and QuerySetPaginator into a single class. Are we not doing that because it'd mean importing django.db into a django.core object? Is there some other way we can point the gun away from our foot? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
