Hey guys,
I figured I'd just chime in here.
Over in DyND-town, we've spent a lot of time figuring out how to structure
DyND callables, which are actually more general than NumPy gufuncs. We've
just recently got them to a place where we are very happy, and are able to
represent a wide range of
==
Announcing bcolz 1.0.0 RC2
==
What's new
==
Yeah, 1.0.0 is finally here. We are not introducing any exciting new
feature (just some optimizations and bug fixes), but bcolz is already 6
years old and it implements most of the
There is certainly good precedent for the approach you suggest.
Shortly after Nathaniel mentioned the rewrite to me, I looked up
d-pointers as a possible technique: https://wiki.qt.io/D-Pointer.
If we allow arbitrary kwargs for the new functions, is that something
you would want to note in the
I have started discussing with Nathaniel the implementation of the ufunc
ABI break that he proposed in a draft NEP a few months ago:
http://thread.gmane.org/gmane.comp.python.numeric.general/61270
His original proposal was to make the public portion of PyUFuncObject be:
typedef struct {
Cool!
But I'm having trouble implementing this, could you provide an example on
how exactly to do this? I'm not sure how to create the appropriate tuple and
how to use it with PyObject_GetItem given an PyArrayObject, unless I'm
misunderstood.
Much appreciated,
Matthew
--
View this message in
=
Announcing Numexpr 2.5.1
=
Numexpr is a fast numerical expression evaluator for NumPy. With it,
expressions that operate on arrays (like "3*a+4*b") are accelerated
and use less memory than doing the same calculation in Python.
It wears