#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 Tim Graham):
I don't have much expertise but reading the documentation, it sounds like
you may be [https://docs.djangoproject.com/en/dev/topics/i18n/timezones
/#interpretation-of-naive-datetime-objects creating invalid data]. Django
converts datetimes when `USE_TZ` is activate, I don't think it can hide
that exception. Did you carefully review the pytz documentation which
states, "Unfortunately using the tzinfo argument of the standard datetime
constructors ‘’does not work’’ with pytz for many timezones."
--
Ticket URL: <https://code.djangoproject.com/ticket/29754#comment:2>
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.23fec88e135e0b5c1eb44d2aa8c0898f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
