On Tue, Aug 18, 2015 at 7:39 AM, Ethan Furman <[email protected]> wrote:
> On 08/17/2015 02:16 PM, Guido van Rossum wrote: > >> On Mon, Aug 17, 2015 at 1:46 PM, Alexander Belopolsky wrote: >> > > Well, everyone implementing a tzinfo class will be confronted with the >> question >> whether to provide those special methods or not. And they may well be >> copy/pasting >> code that implements them. So my claim is that this makes the life of >> everyone >> implementing a tzinfo a little more complex, not just that of tzinfo >> implementers >> who actually need this protocol. Just like the mere existence of >> __length_hint__ >> serves as a distraction for anyone implementing an iterator. >> > > Having briefly read PEP 500 it seems to me the primary use case is the DST > transition; I can easily imagine experiments, studies, laboratory > processes, etc., that need to be aware of how many hours have/will have > passed, and being off by that one hour (or 30 minutes, or whatever) is > simply not acceptable. > Yes, but there are other options. PEP 500 allows way more freedom than is needed. -- --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/
