[Numpy-discussion] Time Zones and datetime64
Chris Barker - NOAA Federal
Wed Apr 17 19:36:19 CDT 2013
On Fri, Apr 12, 2013 at 1:36 PM, Anthony Scopatz <firstname.lastname@example.org> wrote:
> Option (2), what datetime does, is the wrong model. This is more
> complicated in both the implementation and API, and leads to lots of broken
> code, weird errors, and no clear right way of doing thing.
could you elaborate a bit more? I've never tried to use timezone
support with datetime, so I have no idea what goes wrong -- but it
looks reasonable to me. though it really punts on the hard stuff, so
maybe no point.
> Be Well
> On Fri, Apr 12, 2013 at 2:57 PM, Chris Barker - NOAA Federal
> <email@example.com> wrote:
>> On Fri, Apr 12, 2013 at 9:52 AM, Riccardo De Maria
>> <firstname.lastname@example.org> wrote:
>> > Not related to leap seconds and physically accurate time deltas, I have
>> > just
>> > noticed that SQLite has a nice API:
>> > http://www.sqlite.org/lang_datefunc.html
>> > that one can be inspired from. The source contains a date.c which looks
>> > reasonably clear.
>> well, I don't see any timezone support in there at all. It appears the
>> use UTC, though I"m not entierly sure from the docs what now() would
>> So I think it's pretty much like my "use UTC" proposal.
>> Christopher Barker, Ph.D.
>> 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
>> NumPy-Discussion mailing list
> NumPy-Discussion mailing list
Christopher Barker, Ph.D.
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
More information about the NumPy-Discussion