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 -~----------~----~----~----~------~----~------~--~---
