I\'m building an app that would serve people located in different places arround the world.
I\'m using Django-Rest-Framwork for the communication between the clients and
Since Django REST Framework v3.8.0(released in May, 2018), you don't need a custom DateTimeField any more.
In previous versions, Django REST Framework only convert native datetime to timezone aware datetime when parsing the date(DateTimeField.to_internal_value()
), but do not convert when rendering the datatime field(DateTimeField.to_representation()
). This is fixed in DRF v3.8.0.
You may need to change the following settings:
USE_TZ
must be TrueTIME_ZONE
to specify a default timezoneREST_FRAMEWORK.DATETIME_FORMAT
to the format that fits your frontend code. I had the same problem and solved it by adding new type of field:
class DateTimeTzAwareField(serializers.DateTimeField):
def to_native(self, value):
value = timezone.localtime(value)
return super(DateTimeTzAwareField, self).to_native(value)
and now you can use it in ModelSerializer
:
class XSerializer(serializers.ModelSerializer):
start = DateTimeTzAwareField()
end = DateTimeTzAwareField()
class Meta:
model = XModel
fields = (
'id',
'start',
'end',
)
The answer by @yakxxx seems to be the best solution. I am posting it again after updating it to work with newer versions of restframework
inside my directory (common/serializers.py)
from rest_framework import serializers
from django.utils import timezone
class DateTimeFieldWihTZ(serializers.DateTimeField):
def to_representation(self, value):
value = timezone.localtime(value)
return super(DateTimeFieldWihTZ, self).to_representation(value)
Inside my application
from common.serializers import DateTimeFieldWihTZ
class MyObjectSerializer(serializers.ModelSerializer):
start = DateTimeFieldWihTZ(format='%d %b %Y %I:%M %p')
end = DateTimeFieldWihTZ(format='%d %b %Y %I:%M %p')