From 96a15a2d86eabcbbb47374d87f804404d3a08dbf Mon Sep 17 00:00:00 2001 From: Charles Harris Date: Tue, 7 Jun 2022 10:01:23 -0600 Subject: MAINT: Small rewrite for clarity. --- numpy/testing/_private/utils.py | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'numpy/testing') diff --git a/numpy/testing/_private/utils.py b/numpy/testing/_private/utils.py index e61e47488..e4f8b9892 100644 --- a/numpy/testing/_private/utils.py +++ b/numpy/testing/_private/utils.py @@ -1476,12 +1476,11 @@ def assert_allclose(actual, desired, rtol=1e-7, atol=0, equal_nan=True, Raises an AssertionError if two objects are not equal up to desired tolerance. - Given two array_like objects, check that the shape is equal and all - elements of these objects are equal (but see the Notes for the special - handling of a scalar). An exception is raised at shape mismatch or - conflicting values. In contrast to the standard usage in numpy, NaNs - are compared like numbers, no assertion is raised if both objects have - NaNs in the same positions. + Given two array_like objects, check that their shapes and all elements + are equal (but see the Notes for the special handling of a scalar). An + exception is raised if the shapes mismatch or any values conflict. In + contrast to the standard usage in numpy, NaNs are compared like numbers, + no assertion is raised if both objects have NaNs in the same positions. The test is equivalent to ``allclose(actual, desired, rtol, atol)`` (note that ``allclose`` has different default values). It compares the difference -- cgit v1.2.1