Make floating-point exception error messages slightly more verbose: in
particular, the error message now allows one to distinguish between a
ValueError arising from a singularity (e.g. log(0.)), which would
usually produce +-infinity in non-stop mode, and a ValueError resulting
from an invalid input (e.g. sqrt(-1.)), which would normally produce a
NaN in non-stop mode.
diff --git a/Lib/test/ieee754.txt b/Lib/test/ieee754.txt
index 5a41c8f..a07906c 100644
--- a/Lib/test/ieee754.txt
+++ b/Lib/test/ieee754.txt
@@ -127,31 +127,31 @@
>>> sin(INF)
Traceback (most recent call last):
...
-ValueError: math domain error
+ValueError: math domain error (invalid argument)
>>> sin(NINF)
Traceback (most recent call last):
...
-ValueError: math domain error
+ValueError: math domain error (invalid argument)
>>> sin(NAN)
nan
>>> cos(INF)
Traceback (most recent call last):
...
-ValueError: math domain error
+ValueError: math domain error (invalid argument)
>>> cos(NINF)
Traceback (most recent call last):
...
-ValueError: math domain error
+ValueError: math domain error (invalid argument)
>>> cos(NAN)
nan
>>> tan(INF)
Traceback (most recent call last):
...
-ValueError: math domain error
+ValueError: math domain error (invalid argument)
>>> tan(NINF)
Traceback (most recent call last):
...
-ValueError: math domain error
+ValueError: math domain error (invalid argument)
>>> tan(NAN)
nan
@@ -169,11 +169,11 @@
>>> asin(INF), asin(NINF)
Traceback (most recent call last):
...
-ValueError: math domain error
+ValueError: math domain error (invalid argument)
>>> acos(INF), acos(NINF)
Traceback (most recent call last):
...
-ValueError: math domain error
+ValueError: math domain error (invalid argument)
>>> equal(atan(INF), PI/2), equal(atan(NINF), -PI/2)
(True, True)