[Numpy-discussion] Datetime branch
Charles R Harris
charlesr.harris at gmail.com
Thu Jun 11 14:06:41 EDT 2009
On Thu, Jun 11, 2009 at 11:47 AM, Robert Kern <robert.kern at gmail.com> wrote:
> On Thu, Jun 11, 2009 at 12:39, Charles R
> Harris<charlesr.harris at gmail.com> wrote:
> > On Thu, Jun 11, 2009 at 11:34 AM, Robert Kern <robert.kern at gmail.com>
> >> On Thu, Jun 11, 2009 at 12:29, Charles R
> >> Harris<charlesr.harris at gmail.com> wrote:
> >> > Oh, and slipping the new types in between 64 bit integers and floats
> >> > a
> >> > bit iffy.
> >> Where, specifically? There are several linear orders of types in
> >> numpy. I tried to be careful to do the right thing in each. The enum
> >> numbers are after NPY_VOID, of course, for compatibility.
> > I noticed. I'm not saying it's wrong, just that a linear order lacks
> > descriptive power and is difficult to maintain. I expect you ran into
> > problem when trying to make everything work as you wanted.
> Yes. Now, which place am I slipping in the new types between 64-bit
> integers and floats?
In the ufunc generator. But most of the macros use the type ordering and how
do you control the promotion (or lack thereof) of the various types to/from
the datetime types?
There also seems to be some mechanism for raising errors that has been
added, maybe to loops. I'm not clear on that, did you add some such
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion