From 99922b9175c4ca6acb0f42dd17c01c507cbd94d6 Mon Sep 17 00:00:00 2001 From: Douglas Rudd Date: Thu, 16 Jan 2014 17:34:06 -0600 Subject: [PATCH] Modified test_pow function in computation/tests/test_eval.py to use assert_allclose rather than assert_all_equal to avoid machine precision failures in TestEvalNumexprPandas/Numpy. Fixes issue #5981. --- pandas/computation/tests/test_eval.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pandas/computation/tests/test_eval.py b/pandas/computation/tests/test_eval.py index 073526f526abe..e6d2484a41019 100644 --- a/pandas/computation/tests/test_eval.py +++ b/pandas/computation/tests/test_eval.py @@ -405,13 +405,13 @@ def check_pow(self, lhs, arith1, rhs): self.assertRaises(AssertionError, assert_array_equal, result, expected) else: - assert_array_equal(result, expected) + assert_allclose(result, expected) ex = '(lhs {0} rhs) {0} rhs'.format(arith1) result = pd.eval(ex, engine=self.engine, parser=self.parser) expected = self.get_expected_pow_result( self.get_expected_pow_result(lhs, rhs), rhs) - assert_array_equal(result, expected) + assert_allclose(result, expected) @skip_incompatible_operand def check_single_invert_op(self, lhs, cmp1, rhs):