> TIME_ZONE = 'America/Los_Angeles'
This actually led to the solution, which was a stupid error on my
part. Somehow TIME_ZONE got into my settings.py file twice and I was
changing the first instance, which was getting overwritten with the
second instance (default Chicago TZ) later.
--
You rec
Try changing time zones in your settings.py
For example:
TIME_ZONE = 'America/Los_Angeles'
And make sure if you're running on Windows it matches your system's
time zone. Regardless, you should see some kind of change when you do
this. If you don't perhaps the settings.py isn't loading properly.
> Works fine here with Django 1.0.2-1+lenny1; which version do you have?
Django 1.2.1 (installed manually, not through apt) on Kubuntu 10.04,
Python 2.6.5, Postgres 8.4.4.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
On Thu, Jul 29, 2010 at 07:33:26AM -0700, Alex wrote:
> system time zone is EDT and when running datetime.now( ) from a
> *Python* shell I get the correct time. If I run a Django shell
> through manage.py it is an hour behind.
Works fine here with Django 1.0.2-1+lenny1; which version do you have?
I'm having some strange behavior when using Django and Postgres. My
system time zone is EDT and when running datetime.now( ) from a
*Python* shell I get the correct time. If I run a Django shell
through manage.py it is an hour behind. I similarly have set up a
view on a web page to display the t
5 matches
Mail list logo
