#24937: DateTimeRangeField.value_to_string raises TypeError
----------------------------------+------------------------------------
Reporter: unklphil | Owner: dracos
Type: Bug | Status: closed
Component: contrib.postgres | Version: 1.8
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"3ded51bcf21f384b2e80ce97aff5c12d63e5f0e3" 3ded51bc]:
{{{
#!CommitTicketReference repository=""
revision="3ded51bcf21f384b2e80ce97aff5c12d63e5f0e3"
[1.8.x] Fixed #24937 -- Fixed serialization of Date(Time)RangeField.
Use the DjangoJSONEncoder so that datetime and date are encoded
appropriately.
Backport of 2926559cce34e48efb4b073721926d737e372dd3 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24937#comment:7>
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/066.03ca7e9dd083924d642ffa12143e38cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
