diff options
| author | Brightcells <brightcells@gmail.com> | 2016-08-19 18:02:13 +0800 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-08-19 09:16:31 -0400 |
| commit | 557c1a6a4203e16eb826542d441f0968046e5d4c (patch) | |
| tree | 7ce429bfd65f93780d129adbfa1cbe68ada99a3f | |
| parent | a033b351b5234db6170ca93ab102208cd9165820 (diff) | |
[1.10.x] Replaced old DateTimeAwareJSONEncoder with DjangoJSONEncoder in docs.
Backport of d301c61bcb72af864229e51d2ebc6076bea1e5ff from master
| -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 32d3c48713..ab6edd2dc9 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 |