Skip to content Skip to sidebar Skip to footer

Django Timezone Localization Not Working As Expected

I'm using Django 1.4.3 and Postgres 9.1.3. Here is my template where message.created_at is a python datetime object and it clearly tells me that the datetime object is stored in GM

Solution 1:

Are you doing an activate to activate the local time-zone? See this.


Solution 2:

Okay. Considering these posts post#1, post#2 I'm gonna get the timezone manually from the user while signup and store it in database. And will go with timezone.activate(request.user.timezone).


Post a Comment for "Django Timezone Localization Not Working As Expected"