On Thu, Jul 30, 2015 at 12:40 PM, Alexander Belopolsky < [email protected]> wrote:
> On Thu, Jul 30, 2015 at 3:23 PM, Chris Barker <[email protected]> > wrote: > > But we need to (a) be really clear in the docs whether the flag is > consulted > > any any other time. and (b) probably be really careful in the code to > make > > sure the flag is set appropriately at all times. > > "This member will have the value True for all instances except those > that represent the second (chronologically) moment in time in an > ambiguous case." [1] > > Does this require any more clarification? well, it certainly would if it were named somethign like "is_dst", but in the intereast of abslute calrity, how about we add something like: "This member can not be set to force the DST adjustment to behave any differently than the tzinfo object implements it." and/or "This member is not an indicator of whether DST is currently in effect, but is only an indicator or which offset to use in ambiguous cases." -Chris > If so, can you suggest it? > > [1]: https://github.com/abalkin/ltdf/blob/master/README.rst#the-first-flag > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected]
_______________________________________________ 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/
