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 com
Hello everyone,
I'm pleased to announce the latest 0.7.1 release of DyND. The release notes
are at https://github.com/libdynd/libdynd/blob/master/docs/release_notes.txt
.
Over the last 6 months, DyND has really matured a lot and many features
that were "experimental" before are quite usable at th
On Wed, Aug 26, 2015 at 6:11 PM, Antoine Pitrou wrote:
> One possible limitation is that the lingua franca for language
> interoperability is C, not C++. DyND doesn't have to be written in C,
> but exposing a nice C API may help make it attractive to the various
> language runtimes out there.
>
Hello everyone,
Mark and I thought it would be good to weigh in here and also be explicitly
around to discuss DyND. To be clear, neither of us has strong feelings on
what NumPy *should* do -- we are both long-time NumPy users and we both see
NumPy being around for a while. But, as Francesc mention
Hi all,
I've been having an issue with f2py simply ignoring the fortranname
option if the Fortran subroutine is inside an F90 module. That option is
useful for renaming Fortran subroutines.
I don't know if this behaviour is to be expected, or if I am doing
something wrong. I would definitely a
Hi all,
I am writing a C extension for NumPy that implements a custom function.
I have a minor question about iterators, and their order of iteration,
that I would really appreciate some help with. Here goes...
My function takes a sequence of N-dimensional input arrays and a single
(N+1)-dimensio