On mips, 1**np.nan and np.nan**0 may be NaN not 1
authorDebian Science Team <debian-science-maintainers@lists.alioth.debian.org>
Mon, 21 Oct 2024 18:43:11 +0000 (19:43 +0100)
committerRebecca N. Palmer <rebecca_palmer@zoho.com>
Mon, 21 Oct 2024 18:43:11 +0000 (19:43 +0100)
commit1519bc9a674c93f1b6bb34e676db3847fcf3088d
treef0606ea59429a369a367992f4d161236873ff2ec
parentc1b6e788ede151df5c34a4722a7aa2a514bab1bd
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