#17580: DateTimeFields don't handle timezones when given datetime.date instances
---------------------------------+---------------------------------------
Reporter: jezdez | Owner: aaugustin
Type: Bug | Status: new
Component: Core (Other) | Version: 1.4-alpha-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+---------------------------------------
Comment (by aaugustin):
Indeed, a date can't be timezone aware, which means it can't be
interpreted unambiguously as a timezone aware datetime.
That's why I proposed to raise a warning when `USE_TZ = True`, exactly
like I do when a `DateTimeField` receives a naive datetime.
--
Ticket URL: <https://code.djangoproject.com/ticket/17580#comment:3>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
