#19929: "USE_TZ = True" causes error
-----------------------------------+--------------------------------------
Reporter: tomas_00 | Owner: aaugustin
Type: Bug | Status: assigned
Component: Uncategorized | Version: master
Severity: Normal | Resolution:
Keywords: datetime,timzone, | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by aaugustin):
Yes, that explains the problem.
It's documented as a backwards incompatible change in the release notes
for 1.6: https://docs.djangoproject.com/en/dev/releases/1.6/#backwards-
incompatible-changes-in-1-6
See also the note here:
https://docs.djangoproject.com/en/dev/ref/models/querysets/#datetimes
I propose to:
- add a note in the docs for `date_hierarchy` pointing out this caveat,
- test for `None` values and raise an exception with an explicit message
("check that your database has a definition for your current time
zone...")
Does that sound sufficient?
--
Ticket URL: <https://code.djangoproject.com/ticket/19929#comment:8>
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].
For more options, visit https://groups.google.com/groups/opt_out.
