Re: [matplotlib-devel] Date overhaul?

[Chris B. <chr...@no...>]

On Wed, Jan 7, 2015 at 2:10 PM, Eric Firing <ef...@ha...> wrote:

>   One thing that has held this up is that datetime64
> came into numpy half-baked, and has remained experimental with known
> problems that need to be fixed.  It looks like the core of datetime64,
> ignoring timezone problems, isn't going to change, so it should be
> possible to work with that in matplotlib.
>

you can do some googling, but the issue with timezones in datetime64 is
that is _always_ uses the system timezone to translate when parsing iso
strings (and bare datetime.datetime objects) without a timezone, and I'm
pretty sure does somethign like that when formatting string output, too.

It can be worked around if you are careful to always make it think you are
working in UTC.

This should change in a release or two (and I'm sorry to say that I've held
that up by stalling on getting proposals properly written up), but Eric's
right, the internals should stay close enough that it's worth using.

-Chris


-- 

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

Chr...@no...