[Datetime-SIG] PEP-495 - Strict Invalid Time Checking

Alexander Belopolsky alexander.belopolsky at gmail.com
Tue Aug 25 20:42:53 CEST 2015

On Tue, Aug 25, 2015 at 1:56 PM, Stuart Bishop <stuart at stuartbishop.net>

> On 25 August 2015 at 21:51, Alexander Belopolsky
> <alexander.belopolsky at gmail.com> wrote:
> > On Tue, Aug 25, 2015 at 9:30 AM, Stuart Bishop <stuart at stuartbishop.net>
> > wrote:
> >>
> >> As mentioned elsewhere, pytz requires strict checking to remain
> >> backwards compatible.
> >
> > Can you provide the specific examples where strict checking is required?
> Systems where it is better to fail than continue with incorrect
> results. For example, ingesting transaction logs. It is more desirable
> for the script parsing the log files to fail with a traceback than to
> feed incorrect results into the rest of the system, where some poor
> DBA is going to have to repair the cascade of damage months or years
> later.

Speaking of DBAs, how would she feel if a system zoneinfo upgrade made her
database unreadable?   A zoneinfo upgrade can easily create new gaps and
folds even in the past if someone at IANA decides that they found a better
source of historical information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/datetime-sig/attachments/20150825/fe86f637/attachment.html>

More information about the Datetime-SIG mailing list