On mips, 1**np.nan and np.nan**0 may be NaN not 1
authorDebian Science Team <debian-science-maintainers@lists.alioth.debian.org>
Fri, 11 Oct 2024 09:18:43 +0000 (10:18 +0100)
committerRebecca N. Palmer <rebecca_palmer@zoho.com>
Fri, 11 Oct 2024 09:18:43 +0000 (10:18 +0100)
commit5232f1fe2c8ed83c2353827321a7143b87e0daaa
treebddc63da4805f8baa6fac887d3f7ce0981a534b7
parent80381d0b66147aa54d9df0d2b39969154011e075
On mips, 1**np.nan and np.nan**0 may be NaN not 1

Done this way not a plain xfail to allow only this difference,
not clearly wrong answers

(The same hardware's "invalid value encountered" warnings,
probably from sNaN/qNaN being reversed, are ignored elsewhere:
d/rules and xfail_tests_nonintel_io.patch)

https://en.wikipedia.org/wiki/NaN#Encoding

Author: Rebecca N. Palmer <rebecca_palmer@zoho.com>
Forwarded: no

Gbp-Pq: Name mips_pow_nan.patch
pandas/tests/arrays/floating/test_arithmetic.py
pandas/tests/arrays/sparse/test_arithmetics.py