#1480: Don't Set TIME_ZONE unless it is explictly needed (or put it back to how
you found it)
-------------------------------+--------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Core framework
Version: | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------+--------------------------------------------
Changes (by mtredinnick):
* stage: Design decision needed => Accepted
Comment:
This is hard to fix for all cases. It's not ideal that Django wants to set
the timezone everywhere on shared systems, but it's also possible to work
around as a few comments have indicated
The solution we should implement here is to allow the TIMEZONE setting to
be None (or unset), in which case we will not attempt to set the timezone
-- it will remain in the server's timezone -- and the client code is
responsible for doing any timezone manipulations they want to do.
--
Ticket URL: <http://code.djangoproject.com/ticket/1480#comment:7>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
