On Thu, Jan 22, 2015 at 8:08 AM, Charles R Harris <[email protected] > wrote:
> > > On Thu, Jan 22, 2015 at 7:54 AM, Nathaniel Smith <[email protected]> wrote: > >> On Thu, Jan 22, 2015 at 2:51 PM, Charles R Harris >> <[email protected]> wrote: >> > Hi All, >> > >> > I'm playing with the idea of building a simplified datetime class on >> top of >> > the current numpy implementation. I believe Pandas does something like >> this, >> > and blaze will (does?) have a simplified version. The reason for the new >> > class would be to have an easier, and hopefully more portable, API that >> can >> > be implemented in Python, and maybe pushed down into C when things >> settle. >> >> When you say "datetime class" what do you mean? A dtype? An ndarray >> subclass? A python class representing a scalar datetime that you can >> put in an object array? ...? >> > > I was thinking an ndarray subclass that is based on a single datetime > type, but part of the reason for this post is to elicit ideas. I'm > influenced by Mark's discussion apropos blaze > <https://github.com/ContinuumIO/blaze/blob/master/docs/design/blaze-datetime.md>. > I thought it easier to start such a project in python, as it is far easier > for people interested in the problem to work with. > And if I had my druthers, it would use quad precision floating point at it's heart. The 64 bits of long long really isn't enough and leads to all sorts of compromises. But that is probably a pipe dream. Chuck
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
