Matthew Brett wrote: >>> So, currently we have all and allclose giving the same answer: >>> >>> In [19]: a = array([]) >>> >>> In [20]: b = array([1]) >>> >>> In [21]: all(a == b) >>> Out[21]: True >>> >>> In [22]: allclose(a, b) >>> Out[22]: True >>> >>> Would we want the answers to be different? >>> >> No. I wasn't thinking correctly, previously. >> > > It's unfortunate that all of us immediately think the given answer is wrong. Maybe we need "allclose_sameshape()" (my ability to name stuff is terrible, but you get the idea). Regardless of the name issue, I have no idea how this is viewed against the no-namespace-bloat principle. _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
- Re: [Numpy-discussion] unexpected behavior with allclose(... Robert Kern
- Re: [Numpy-discussion] unexpected behavior with allc... Charles R Harris
- Re: [Numpy-discussion] unexpected behavior with ... Alan G Isaac
- Re: [Numpy-discussion] unexpected behavior w... Alan G Isaac
- Re: [Numpy-discussion] unexpected behavior with ... Matthew Brett
- Re: [Numpy-discussion] unexpected behavior w... Matthew Brett
- Re: [Numpy-discussion] unexpected behavi... Charles R Harris
- Re: [Numpy-discussion] unexpected b... Matthew Brett
- Re: [Numpy-discussion] unexpect... Robert Kern
- Re: [Numpy-discussion] unexpect... Matthew Brett
- Re: [Numpy-discussion] unexpect... Andrew Straw
- Re: [Numpy-discussion] unexpected behavior with allclose(... Andrew Straw
- Re: [Numpy-discussion] unexpected behavior with allc... Charles R Harris
- Re: [Numpy-discussion] unexpected behavior with ... Andrew Straw