#11321: Bug with humanize and timezones
-------------------------------------+-------------------------------------
Reporter: aarond10 | Owner: nobody
Type: Bug | Status: new
Component: contrib.humanize | Version: master
Severity: Normal | Resolution:
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 gabn88):
* status: closed => new
* ui_ux: => 1
* resolution: fixed =>
* easy: => 1
Comment:
To be honoust I still don't like the solution.
It means you have to create a custom Date object (that inherits from
datetime.date), where you manually set the tzinfo attribute.
I think using timezone.get_current_timezone() would be much more
convenient!
--
Ticket URL: <https://code.djangoproject.com/ticket/11321#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 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.578498b69bbf3cc47c5594dc0aa6f78f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
