#29754: Trunc() doesn't handle NonExistentTimeError/AmbiguousTimeError
-------------------------------------+-------------------------------------
Reporter: Alexander Holmbäck | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: pytz, Trunc() | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Alexander Holmbäck):
Thanks Tim for the valid input, but the situation remains even with dates
constructed according to pytz documentation, which I hadn't carefully read
;-)
Btw, here's possible solution:
[https://github.com/django/django/pull/10390 PR].
If this is a no-go, I think the test
[https://github.com/django/django/blob/master/tests/admin_views/tests.py#L942
admin_views.tests.AdminViewBasicTest.test_date_hierarchy_timezone_dst]
should be changed so that it expects an exception. Otherwise the date
hierarchy tag is bound to only deal with non-local times (which leads to
#29724).
--
Ticket URL: <https://code.djangoproject.com/ticket/29754#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.31c2033ec27ca41d4ce105727db115e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
