#2386: [patch]previous_month and previous_day are non-empty even if there are no
objects in previous months/days
------------------------------------------------------+---------------------
Reporter: Tyson Tate <[EMAIL PROTECTED]> | Owner: jacob
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: Generic views | Version: SVN
Severity: normal | Resolution:
Keywords: previous_month previous_day genericviews |
------------------------------------------------------+---------------------
Changes (by jacob):
* resolution: fixed =>
* status: closed => reopened
Comment:
Good patch, Pete!
I'm not so hot on the idea of only returning next/prev in the current
year/month; seems like that would bite me in the ass when dealing with Jan
1st :). Think you could rework the patch to always return the next/prev
month/day (if it exists) reguardless of current year/month?
(Oh, and marking it fixed is a little premature; we still gotta apply the
patch :)
--
Ticket URL: <http://code.djangoproject.com/ticket/2386>
Django <http://code.djangoproject.org/>
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 this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
