Opened 17 years ago
Closed 17 years ago
#5781 closed (invalid)
Timeuntil filter doesn't work as expected
| Reported by: | Luca Lenardi | Owned by: | nobody |
|---|---|---|---|
| Component: | Template system | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Timeuntil doesn't consider the timezone of the date passed.
While timesince takes care of the timezone when creating the "now" date for comparison, timeuntil calls timesince with d = now, but without considering timezone.
Change History (2)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Closing, based on lack of feedback to previous comment. As far as I can tell, the timeuntil filter is working as expected (we are even testing that).
Note:
See TracTickets
for help on using tickets.
I'm not sure I understand the problem you are seeing.
datetime.datetime.now()is already in the local timezone and Django sets up the environment so that local time is the zone given in settings.py. So we are implicitly taking the timezone into account.Can you give an example showing the problem, please.