Finally found this link: http://www.postgresql.org/docs/8.1/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE on the django project site @ http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#time-zone
On May 19, 9:28 pm, Chris Moffitt <[email protected]> wrote: > Satchmo itself doesn't care about the timezones. Django does but I'm not > 100% sure where. I'd suggest the satchmo skeleton list as a start. > > -Chris > > > > > > On Wed, May 19, 2010 at 9:20 PM, Mark Jones <[email protected]> wrote: > > I'm hooking Feincms together with Satchmo > > > I have two conflicting lists of timezones: > > > # Local time zone for this installation. Choices can be found here: > > #http://en.wikipedia.org/wiki/List_of_tz_zones_by_name > > # although not all choices may be available on all operating systems. > > # On Unix systems, a value of None will cause Django to use the same > > # timezone as the operating system. > > # If running in a Windows environment this must be set to the same as > > your > > # system time zone. > > TIME_ZONE = 'America/Chicago' > > > and > > > # Local time zone for this installation. All choices can be found > > here: > > # > >http://www.postgresql.org/docs/current/static/datetime-keywords.html#... > > TIME_ZONE = 'US/Pacific' > > > Which one should I use? It seems that the only places that care are > > in postgresql and in utils.py > > > grep -R --include=*.py "TIME_ZONE" . > > ./example/settings.py:TIME_ZONE = 'America/Chicago' > > ./Lib/site-packages/django/conf/global_settings.py:TIME_ZONE = > > 'America/Chicago' > > ./Lib/site-packages/django/conf/project_template/settings.py:TIME_ZONE > > = 'America/Chicago' > > ./Lib/site-packages/django/conf/__init__.py: > > os.environ['TZ'] = self.TIME_ZONE > > ./Lib/site-packages/django/db/backends/postgresql/base.py: > > cursor.execute("SET TIME ZONE %s", [settings_dict[ > > 'TIME_ZONE']]) > > ./Lib/site-packages/django/db/backends/postgresql_psycopg2/ > > base.py: cursor.execute("SET TIME ZONE %s", [setti > > ngs_dict['TIME_ZONE']]) > > ./Lib/site-packages/django/db/utils.py: > > conn.setdefault('TIME_ZONE', settings.TIME_ZONE) > > ./Lib/site-packages/django/db/__init__.py:# settings that the database > > backends care about. Note that TIME_ZONE is used > > ./Lib/site-packages/django/db/__init__.py: 'TIME_ZONE': > > settings.TIME_ZONE, > > ./Lib/site-packages/Satchmo-0.9_1-py2.6.egg/satchmo_skeleton/ > > settings.py:TIME_ZONE = 'US/Pacific' > > ./src/django-keyedcache/tests/settings.py:TIME_ZONE = 'US/Pacific' > > ./src/django-livesettings/tests/settings.py:TIME_ZONE = 'US/Pacific' > > ./src/django-signals-ahoy/tests/settings.py:TIME_ZONE = 'US/Pacific' > > ./src/django-threaded-multihost/tests/settings.py:TIME_ZONE = 'America/ > > Chicago' > > ./store/settings.py:TIME_ZONE = 'US/Pacific' > > ./website/settings.py:TIME_ZONE = 'America/Chicago' > > > I'm leaning toward the list from the satchmo skeleton.... > > > -- > > You received this message because you are subscribed to the Google Groups > > "Satchmo users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<satchmo-users%2bunsubscr...@goog > > legroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/satchmo-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Satchmo users" 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 > athttp://groups.google.com/group/satchmo-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en.
