[Numpy-discussion] Allowing broadcasting of code dimensions in generalized ufuncs

Matthew Harrigan harrigan.matthew at gmail.com
Fri Jun 1 13:19:00 EDT 2018

Stephan, good point about use cases.  I think its still an odd fit.  For
example I think np.array_equal(np.zeros((3,3)), np.zeros((2,2))) or
np.array_equal([1], ['foo']) would be difficult or impossible to replicate
with a potential all_equal gufunc

On Thu, May 31, 2018 at 2:00 PM, Stephan Hoyer <shoyer at gmail.com> wrote:

> On Wed, May 30, 2018 at 5:01 PM Matthew Harrigan <
> harrigan.matthew at gmail.com> wrote:
>> "short-cut to automatically return False if m != n", that seems like a
>> silent bug
> I guess it depends on the use-cases. This is how np.array_equal() works:
> https://docs.scipy.org/doc/numpy/reference/generated/
> numpy.array_equal.html
> We could even imagine incorporating this hypothetical "equality along some
> axes with broadcasting" functionality into axis/axes arguments for
> array_equal() if we choose this behavior.
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20180601/a0f39bec/attachment.html>

More information about the NumPy-Discussion mailing list