From d301c61bcb72af864229e51d2ebc6076bea1e5ff Mon Sep 17 00:00:00 2001 From: Brightcells Date: Fri, 19 Aug 2016 18:02:13 +0800 Subject: [PATCH] Replaced old DateTimeAwareJSONEncoder with DjangoJSONEncoder in docs. --- docs/topics/http/sessions.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt index 0b48853bba..39c64f525d 100644 --- a/docs/topics/http/sessions.txt +++ b/docs/topics/http/sessions.txt @@ -373,7 +373,7 @@ including ``datetime`` and ``Decimal`` in JSON backed sessions, you will need to write a custom serializer (or convert such values to a JSON serializable object before storing them in ``request.session``). While serializing these values is fairly straightforward -(``django.core.serializers.json.DateTimeAwareJSONEncoder`` may be helpful), +(:class:`~django.core.serializers.json.DjangoJSONEncoder` may be helpful), writing a decoder that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a ``datetime`` that was actually a string that just happened to be in the same format chosen for