#8453: Error in filter "timesince"
--------------------------------------+-------------------------------------
Reporter: carlou | Owner: jheasly
Status: closed | Milestone: 1.0
Component: Template system | Version: 1.0-beta-1
Resolution: invalid | Keywords: timesince
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by kevin):
* status: assigned => closed
* resolution: => invalid
Comment:
I discussed this ticket with Malcolm. The current behavior could indeed
be considered to be somewhat surprising, in that `value` is typically
expected to be older than `now()` in the default case, yet is expected to
be the newer of the two times where a reference point other than `now()`
is supplied. In effect, the meaning of `arg` and `value` are reversed
when a reference point is supplied.
That said, the current situation works correctly as documented, and
existing code may depend on its behavior. It's not considered to be a
bug.
--
Ticket URL: <http://code.djangoproject.com/ticket/8453#comment:3>
Django Code <http://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 this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
