#11321: Bug with humanize and timezones
-------------------------------------+-------------------------------------
Reporter: aarond10 | Owner: nobody
Type: Bug | Status: closed
Component: contrib.humanize | Version: master
Severity: Normal | Resolution: fixed
Keywords: humanize, | Triage Stage: Accepted
naturalday, timezone |
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => fixed
Comment:
This ticket was closed 5 years ago, before Django gained support for
timezones in version 1.4. The naturalday filter was refactored in that
version.
Given that the landscape has changed significantly since this ticket was
discussed, it would be best to open a new ticket and explain the problem
you see in the current implementation.
That will make it more likely that someone will understand what you want
to do and make it happen. Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/11321#comment:8>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.092e2cf6b16e58bc872387518f5d44d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
