Anyone using settings.TIME_ZONE=None? (considering remove support for it)

I'm not sure if there's a compelling use case for settings.TIME_ZONE=None these days. If you're using it, could you please describe your use case on the django-developers thread: https://groups.google.com/d/topic/django-developers/OAV3FChfuPM/discussion Thanks! -- You received this message

Re: settings.TIME_ZONE

Ok, turns out when I set TIME_OUT to 'UTC' it was storing and retrieving the dates correctly. But when I was viewing the dates in psql and pgAdmin III it was showing the dates using my system's time zone data. -- You received this message because you are subscribed to the Google Groups "Django

Re: settings.TIME_ZONE

Not only do I have settings.TIME_ZONE set to 'UTC', I'm also creating datetime objects via utcfromtimestamp() as follows: field = datetime.datetime.utcfromtimestamp(time.time()) So I figured they would be going into the database as UTC anyway. When I figured out that they were showing UTC-6

Re: settings.TIME_ZONE

On Dec 6, 9:21 pm, Graham Dumpleton wrote: > Some explanation of this issue in: > >  http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Timezone_and_... > > If using Apache/mod_wsgi, delegate Python web application instances > with specific timezone, locale,

Re: settings.TIME_ZONE

On Dec 6, 8:39 pm, Brian Neal wrote: > What is your server setup? Apache on Linux? mod_python or mod_wsgi? > Are you running anything else on your server like PHP apps? The > timezone setting is process-wide, so depending on how you deployed > your server another application

Re: settings.TIME_ZONE

On Dec 7, 1:39 pm, Brian Neal <bgn...@gmail.com> wrote: > On Dec 6, 7:40 pm, XtraGreen <stargazer...@gmail.com> wrote: > > > I've changed settings.TIME_ZONE to 'UTC' and restarted my server but > > when I create records (postgresql) they're not UTC, they

Re: settings.TIME_ZONE

On Dec 6, 7:40 pm, XtraGreen <stargazer...@gmail.com> wrote: > I've changed settings.TIME_ZONE to 'UTC' and restarted my server but > when I create records (postgresql) they're not UTC, they're 'America/ > Chicago' (-6) in the table. > > Am I missing something or is setti

settings.TIME_ZONE

I've changed settings.TIME_ZONE to 'UTC' and restarted my server but when I create records (postgresql) they're not UTC, they're 'America/ Chicago' (-6) in the table. Am I missing something or is settings.TIME_ZONE useless? -- You received this message because you are subscribed to the Google

Re: settings.TIME_ZONE

It turns out its my stupid host that's not handling the dates properly. I wrote a Python script and tested: #! /usr/bin/env python import os import datetime def do_test(tz): if tz != '': os.environ['TZ'] = tz print '%20s: %s' % (tz, datetime.datetime.today()) [do_test(tz) for tz

Re: settings.TIME_ZONE

Here's more info: $ ./manage.py shell Python 2.5 (r25:51908, Mar 23 2007, 14:22:20) [GCC 3.4.6 20060404 (Red Hat 3.4.6-3)] on linux2 Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from datetime import datetime >>> datetime.today()

settings.TIME_ZONE

I'm a little confused about the TIME_ZONE setting in settings.py. I originally had it set to 'America/New_York', because that's the time zone where I'm located, but I noticed the times were ~4 hours off when I would save an object that had a DateTimeField(auto_now_add=True) field in the model.