[Numpy-discussion] New behavior of allclose

Nathan Goldbaum nathan12343 at gmail.com
Wed Nov 4 14:36:01 EST 2015


I actually brought this up before 1.10 came out:
https://github.com/numpy/numpy/issues/6196

The behavior change brought out a bug in our use of allclose, so while it
was annoying in the sense that our test suite started failing in a new way,
it was good in that our tests are now more correct.

On Wed, Nov 4, 2015 at 1:28 PM, Charles R Harris <charlesr.harris at gmail.com>
wrote:

> Hi All,
>
> This is to open a discussion of a change of behavior of `np.allclose`.
> That function uses `isclose` in numpy 1.10 with the result that array
> subtypes are preserved whereas before they were not. In particular, memmaps
> are returned when at least one of the inputs is a memmap. By and large I
> think this is a good thing, OTOH, it is a change in behavior. It is easy to
> fix, just run `np.array(result, copy=False)` on the current `result`, but I
> thought I'd raise the topic on the list in case there is a good argument to
> change things.
>
> Chuck
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20151104/8639982b/attachment.html>


More information about the NumPy-Discussion mailing list