From da5ce52061be41c1c6882224ce8201b6d35f43b8 Mon Sep 17 00:00:00 2001 From: Gary Wilson Jr Date: Fri, 7 Sep 2007 04:09:59 +0000 Subject: [PATCH] Fixed #3134 -- Made the `archive_year` generic view consistent with the other date-based generic views by not performing an `order_by()` on the passed queryset. This change is backwards-incompatible if you were relying on `archive_year` to do the ordering for you. git-svn-id: http://code.djangoproject.com/svn/django/trunk@6057 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- django/views/generic/date_based.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/django/views/generic/date_based.py b/django/views/generic/date_based.py index c0f219f280..6e6cff5872 100644 --- a/django/views/generic/date_based.py +++ b/django/views/generic/date_based.py @@ -76,7 +76,7 @@ def archive_year(request, year, queryset, date_field, template_name=None, if not date_list and not allow_empty: raise Http404 if make_object_list: - object_list = queryset.filter(**lookup_kwargs).order_by(date_field) + object_list = queryset.filter(**lookup_kwargs) else: object_list = [] if not template_name: