Open GoogleCodeExporter opened 9 years ago
The following path was applied in debian packages to workaround the issue:
http://anonscm.debian.org/gitweb/?p=debian-science/packages/numexpr.git;a=blob;f
=debian/patches/0001-fix-unittests.patch;h=ae4ffc7bb33d48ecb3c668364adb10f58cd05
e64;hb=74ee7bb647d92066658d64d691d64e3aa8e3a7e1
Original comment by a.valent...@gmail.com
on 22 Apr 2012 at 5:41
As per:
http://docs.scipy.org/doc/numpy/reference/generated/numpy.testing.assert_approx_
equal.html
I'd say that it is better to use `assert_close` than `assert_approx_equal`.
See 193acd1c79e5 changeset.
Original comment by fal...@gmail.com
on 22 Apr 2012 at 10:09
Yes, you are right.
Anyway, in the specific case of the debian package we chose to use
assert_approx_equal that is also supported by numpy < 1.5.x.
Original comment by a.valent...@gmail.com
on 23 Apr 2012 at 6:08
Original issue reported on code.google.com by
a.valent...@gmail.com
on 15 Feb 2012 at 8:30