my settings.py :
...
# Local time zone for this installation. All choices can be found here:
#
http://www.postgresql.org/docs/current/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE
TIME_ZONE = 'Europe/Paris'
...
E:\applis\budget>time
L'heure actuelle est : 19:17:58,31
Entrez la nouvelle heure :
E:\applis\budget>manage.py runserver
Validating models...
0 errors found.
Django version 0.96-pre, using settings 'budget.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CTRL-BREAK.
[13/Nov/2006 18:20:03] "GET /budget/2006/08/ HTTP/1.1" 200 35683
It seems to me runserver prints summer time
Has anyone ever notice that ?
Thank you all
jlT
For instance, it's set to the default 'America/Chicago' right now. I
put this in my template:
{% now "Y-m-d H:m:s" %}
It returns:
2006-11-14 15:49:52
My time is actually 07:49:52 - it's 8 hours off which makes sense
because I'm in PST (-08:00). What am I doing wrong?
thx
Gabe
My system clock claims it's on the right time. That's what I'm using
in the above example - 07:49:52 came from the clock in the windows task
bar. However, Django always says it's GMT, no matter what timezone I
set in the settings.py file. It happens on my home computer and my
work computer. Both computers are running python 2.4.4 . One is
running django from the trunk, the other from 0.95.
g
I remember a while back there was a spate of problems with correctly
setting the time-zone environment variable on Windows; I'll dig a bit
through old tickets tonight and see if I can find anything relevant.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
> I dont know why it would use anything other than the system time... Is
> the timezone set correctly on your machine?
time is a DOS command
and it renders the good time, same time i can show under Windows
but Django runserver renders summer time, or GMT ?
Thanks all
jlT
http://code.djangoproject.com/ticket/2315
--
----
Waylan Limberg
way...@gmail.com
Please report if that solves your problem in the above mentioned ticket
(http://code.djangoproject.com/ticket/2315) - if multiple people have
tested and can confirm the fix, it's more likely to get applied.