#24841: BaseRangeField should use base_field's prepare_value method
----------------------------------+-----------------
Reporter: unklphil | Owner:
Type: Bug | Status: new
Component: contrib.postgres | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 1 | UI/UX: 0
----------------------------------+-----------------
The `BaseRangeField` doesn't do the `base_field`'s `prepare_value` method
on the submitted range values, so the base field preparations are not
applied to the values.
For the basic types, this isn't a problem, but for `DateTimeRangeField` it
is, because the `DateTimeField` (`DateTimeRangeField`'s `base_field`) does
a timezone conversion on the submitted values, but `DateTimeRangeField`
leaves the timezone as is.
What then happens is that datetimes displayed by the field are in UTC, but
they are submitted as the local timezone.
--
Ticket URL: <https://code.djangoproject.com/ticket/24841>
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/051.72d8fcea849a51a3ffa012f76265e0d1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
