My server is located in London.
In my settings.py
I have:
TIME_ZONE = 'Europe/Moscow' USE_TZ = True
But when I execute this:
from django.utils import timezone print timezone.now().hour
the code prints London's time. What am I doing wrong?
UPDATE:
>> timezone.now() datetime.datetime(2013, 4, 16, 12, 28, 52, 797923, tzinfo=<UTC>)
Interesting... tzinfo = <UTC>
. So maybe it prints not a London time, but UTC's +0 time? Anyway, is there any way to make Django show Moscow time?
Also when I render template with now = timezone.now()
{{ now.hour }}
prints 12 (London time)
{{ now|date:"G" }}
prints 16 (Moscow time)
timezone. now() useful. This function returns the current date and time as a naive datetime when USE_TZ = False and as an aware datetime when USE_TZ = True .
Django's timezone is set to UTC by default.
Django stores datetime information in UTC in the database, uses timezone-aware datetime objects internally, and translates them to the end user's time zone in templates and forms.
See question #2 in the "Usage" section of the Django docs.
>>> from django.utils import timezone >>> timezone.localtime(timezone.now())
Since the doc above also talks about a best practice, including an excerpt below:
How can I obtain the local time in the current time zone?
Well, the first question is, do you really need to?
You should only use local time when you’re interacting with humans, and the template layer provides filters and tags to convert datetimes to the time zone of your choice.
Furthermore, Python knows how to compare aware datetimes, taking into account UTC offsets when necessary. It’s much easier (and possibly faster) to write all your model and view code in UTC. So, in most circumstances, the datetime in UTC returned by django.utils.timezone.now() will be sufficient.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With