#16218: Class-based month archive doesn't behave like previous generic view
-------------------------------+-------------------------------------
Reporter: nnrcschmdt | Owner: aaugustin
Type: Bug | Status: new
Component: Generic views | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+-------------------------------------
Changes (by aaugustin):
* needs_better_patch: 1 => 0
Comment:
I just reviewed the history of this ticket and updated the patch. Pull
request: https://github.com/django/django/pull/362
The documented order seems much more logical to me than the implemented
order. Like nnrcschmdt and bpeschier, I'd prefer to restore the documented
order, even though it introduces a backwards incompatibility.
As an unscientific datapoint, I always reverse `date_list` in year and
month views in my templates; when we fix this ticket I'll be able to
remove that code.
--
Ticket URL: <https://code.djangoproject.com/ticket/16218#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
