#15091: Ease using a custom JSON encoder with serialize()
-------------------------------------+-------------------------------------
Reporter: knurpsburps | Owner:
| berkerpeksag
Type: New feature | Status: closed
Component: Core | Version: 1.2
(Serialization) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"c1b6f554e405fe733e8d80f7e3d77c277810e707" c1b6f554]:
{{{
#!CommitTicketReference repository=""
revision="c1b6f554e405fe733e8d80f7e3d77c277810e707"
Fixed #15091 -- Allowed passing custom encoder to JSON serializer.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/15091#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.5d418d4a6b1580d1257db7bef3c3d168%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
