#25019: DjangoJSONEncoder does not encode UUIDs
-------------------------------------+-------------------------------------
Reporter: lukas-hetzenecker | Owner: nobody
Type: New feature | Status: closed
Component: Core | Version: master
(Serialization) |
Severity: Normal | Resolution: fixed
Keywords: UUIDField | Triage Stage: Accepted
DjangoJSONEncoder |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by yarbelk):
This also impacts the use of UUID fields in other projects, such as
django-allauth,
https://github.com/pennersr/django-allauth/issues/916
I believe this fix should also be back ported to the 1.8.x branch because
the expected behaviour of 'I serialise my User Model which has a UUID
field' into my session or cache crashes.
Cherry picking this commit into the 1.8.x branch fixed all my problems.
--
Ticket URL: <https://code.djangoproject.com/ticket/25019#comment:4>
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/075.7b6758b59a394f7eeccf3b96ef0f31e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
