You were using a new feature (albeit the wrong one) so that's not really a backwards incompatible issue, is it?
On May 6, 1:55 pm, David Cramer <[EMAIL PROTECTED]> wrote: > Can someone add it to the BackwardsIncompatibeChanges page? > > I saw the warning, and briefly skimmed over the page and switched to > Paginator. To my suprise, there was a little clause at the bottom > saying "USE QUERYSETPAGINATOR" which I didn't notice. You can guess > what I was thinking when I saw it querying 50k rows then slicing it ;) Speaking of the new paginator, I've been thinking that it would be more logical if the PaginatorPage just worked as an iterable. Yes? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
