diff options
| author | Brightcells <brightcells@gmail.com> | 2016-08-19 18:02:13 +0800 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-08-19 09:13:53 -0400 |
| commit | d301c61bcb72af864229e51d2ebc6076bea1e5ff (patch) | |
| tree | fd08308edbde1145aff1d0fbeb80cea305bd6486 | |
| parent | f8c338ec6a372841559e3134cf4d4329c460f8c7 (diff) | |
Replaced old DateTimeAwareJSONEncoder with DjangoJSONEncoder in docs.
| -rw-r--r-- | docs/topics/http/sessions.txt | 2 |
1 files changed, 1 insertions, 1 deletions
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 |