#2626: Datetime handling is broken when dealing with more than one time zone
-------------------------------------+--------------------------------------
Reporter: Tom Tobin | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version:
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by gsong):
I want to make sure I have some basic decisions straight before tackling
this problem. We want to only affect how `datetime.datetime` objects
behave, and '''not''' `datetime.time` and `datetime.date` objects, right?
In other words, only `models.DateTimeField`, '''not''' `models.TimeField`
and `models.DateField`. I don't think timezone conversions are meaningful
in those cases, at least not generally.
Also when I work on this problem, I will follow my proposal in #10587
unless there's any strong objections.
--
Ticket URL: <http://code.djangoproject.com/ticket/2626#comment:20>
Django <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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
