Sounds to me like Tim and Stuart disagree on the definition of conversion, though.
On Mon, Aug 24, 2015 at 5:00 PM, Alexander Belopolsky < [email protected]> wrote: > > On Mon, Aug 24, 2015 at 7:55 PM, Carl Meyer <[email protected]> wrote: > >> But you're changing the subject. That exercise requires far more >> detailed knowledge of the tzinfo APIs than is required to understand >> that a single added disambiguating bit is enough to handle timezone >> conversions, even in the presence of (two-layered) folds and gaps. >> > > Sorry for that. Meanwhile, however Tim has responded and the point that > both of us think is misunderstood is that contrary to Stuart's assertion > below and at the top of this thread, all conversion issues can be addressed > without any change to arithmetic. (Moreover, addressing them with classic > arithmetic is easier.) > > [Stuart Bishop <[email protected]>] > > ... > > Conversion was the larger issue, and to do that correctly the > > arithmetic needed to be fixed. > > _______________________________________________ > Datetime-SIG mailing list > [email protected] > https://mail.python.org/mailman/listinfo/datetime-sig > The PSF Code of Conduct applies to this mailing list: > https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Datetime-SIG mailing list [email protected] https://mail.python.org/mailman/listinfo/datetime-sig The PSF Code of Conduct applies to this mailing list: https://www.python.org/psf/codeofconduct/
