From: Terry Jan Reedy Date: Mon, 16 Jun 2014 07:31:00 +0000 (-0400) Subject: Issue #21559: Add alternative (historical) reason for OverflowError. X-Git-Tag: v3.4.2rc1~381 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b6d1f48c14b7a3bc7047138dc0bf5aadfe6be480;p=python Issue #21559: Add alternative (historical) reason for OverflowError. --- diff --git a/Doc/library/exceptions.rst b/Doc/library/exceptions.rst index d2c2ef4597..74d6fcb78c 100644 --- a/Doc/library/exceptions.rst +++ b/Doc/library/exceptions.rst @@ -274,9 +274,10 @@ The following exceptions are the exceptions that are usually raised. Raised when the result of an arithmetic operation is too large to be represented. This cannot occur for integers (which would rather raise - :exc:`MemoryError` than give up). Because of the lack of standardization of - floating point exception handling in C, most floating point operations also - aren't checked. + :exc:`MemoryError` than give up). However, for historical reasons, + OverflowError is sometimes raised for integers that are outside a required + range. Because of the lack of standardization of floating point exception + handling in C, most floating point operations are not checked. .. exception:: ReferenceError