On Fri, Aug 29, 2014 at 10:55 AM, Jaime Fernández del Río
jaime.f...@gmail.com wrote:
On Thu, Aug 28, 2014 at 5:40 PM, Nathaniel Smith n...@pobox.com wrote:
Some thoughts:
But, for your computed dimension idea I'm wondering if what we should
do instead is just let a gufunc provide a C
On Fri, Aug 29, 2014 at 2:55 AM Jaime Fernández del Río
jaime.f...@gmail.com wrote:
On Thu, Aug 28, 2014 at 5:40 PM, Nathaniel Smith n...@pobox.com wrote:
Some thoughts:
But, for your computed dimension idea I'm wondering if what we should
do instead is just let a gufunc provide a C
On Thu, Aug 28, 2014 at 5:40 PM, Nathaniel Smith n...@pobox.com wrote:
Some thoughts:
But, for your computed dimension idea I'm wondering if what we should
do instead is just let a gufunc provide a C callback that looks at the
input array dimensions and explicitly says somehow which
Hi,
I have just sent a PR (https://github.com/numpy/numpy/pull/5015), adding
the possibility of having frozen dimensions in gufunc signatures. As a
proof of concept, I have added a `cross1d` gufunc to
`numpy.core.umath_tests`:
In [1]: import numpy as np
In [2]: from numpy.core.umath_tests import
On Fri, Aug 29, 2014 at 1:14 AM, Jaime Fernández del Río
jaime.f...@gmail.com wrote:
Hi,
I have just sent a PR (https://github.com/numpy/numpy/pull/5015), adding the
possibility of having frozen dimensions in gufunc signatures. As a proof of
concept, I have added a `cross1d` gufunc to
