Re: Paginator Backwards Compatibility Post
On Tue, May 6, 2008 at 10:12 AM, Collin Grady <[EMAIL PROTECTED]> wrote: > > SmileyChris said the following: > > > You were using a new feature (albeit the wrong one) so that's not > > really a backwards incompatible issue, is it? > > The old ObjectPaginator class is going away though, isn't it? That sounds > like backwards incompatible to me ;) No. Backwards incompatible means that existing code will break and stop working due to a change in API or behaviour. We haven't removed or changed the old paginator, so code that uses it will continue to work. However, that code will raise warnings about the use of a deprecated API. When the old paginator is eventually removed, _that_ will be a backwards incompatible change. Yours, Russ Magee %-) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Paginator Backwards Compatibility Post
SmileyChris said the following: > You were using a new feature (albeit the wrong one) so that's not > really a backwards incompatible issue, is it? The old ObjectPaginator class is going away though, isn't it? That sounds like backwards incompatible to me ;) -- Collin Grady Computer programmers never die, they just get lost in the processing. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Paginator Backwards Compatibility Post
Well it's deprecated. If nothing else, can we have a "OMGBIGCHANGES" wiki page? :) In regards to features. I could make quite a few suggestions for the paginator based on my use-cases at Curse and other projects. The new one is a big improvement, but I find that I still can't use it without subclassing. If it's not an iterable though, probably should be :) On May 5, 6:59 pm, SmileyChris <[EMAIL PROTECTED]> wrote: > 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 -~--~~~~--~~--~--~---
Re: Paginator Backwards Compatibility Post
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 -~--~~~~--~~--~--~---
Paginator Backwards Compatibility Post
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 ;) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
