[Django Code] #6822: date_based.archive_index should append _list to template_object_name

0 views
Skip to first unread message

Django Code

unread,
Mar 18, 2008, 5:25:44 PM3/18/08
to djang...@holovaty.com, ja...@jacobian.org, django-...@googlegroups.com
#6822: date_based.archive_index should append _list to template_object_name
-----------------------+----------------------------------------------------
Reporter: minarets | Owner: nobody
Status: new | Component: Generic views
Version: SVN | Keywords:
Stage: Unreviewed | Has_patch: 0
-----------------------+----------------------------------------------------
django.views.generic.date_based.archive_index is inconsistent in its
handling of the template_object_name variable. The other views will append
'_list' to the value of this parameter in determining the variable’s name
(archive_year, archive_week, archive_month, archive_day). The
archive_index view should be changed to reflect this behavior.

--
Ticket URL: <http://code.djangoproject.com/ticket/6822>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines

Django Code

unread,
Mar 19, 2008, 12:20:55 AM3/19/08
to djang...@holovaty.com, ja...@jacobian.org, django-...@googlegroups.com
#6822: date_based.archive_index should append _list to template_object_name
------------------------+---------------------------------------------------
Reporter: minarets | Owner: nobody
Status: closed | Component: Generic views
Version: SVN | Resolution: duplicate
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------+---------------------------------------------------
Changes (by ramiro):

* status: new => closed
* needs_better_patch: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0

Comment:

This has been proposed before in #4619 and backward compatibility was
deemed more important so that ticket got wontfix'ed. See also #3895 and
[6157].

--
Ticket URL: <http://code.djangoproject.com/ticket/6822#comment:1>
Reply all
Reply to author
Forward
0 new messages