#2626: Datetime handling is broken when dealing with more than one time zone
-------------------------------------+--------------------------------------
Reporter: Tom Tobin | Owner: nobody
Status: new | Milestone: post-1.0
Component: Core framework | Version:
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by subsume):
I only see the SQL element being discussed, however, there is a more
general problem where even datetime.now() will (randomly?) report
incorrectly.
Using Apache and both mod_python and wsgi I find that various uses of
datetime.now() around a project will give another TZ.
--
Ticket URL: <http://code.djangoproject.com/ticket/2626#comment:16>
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 [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
-~----------~----~----~----~------~----~------~--~---
