From bafa9425a61e7584e4a3b15a5148371010970da7 Mon Sep 17 00:00:00 2001 From: Mark Dickinson Date: Wed, 6 Feb 2008 22:25:16 +0000 Subject: Remove incorrect usage of :const: in documentation. --- Doc/library/decimal.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/library/decimal.rst b/Doc/library/decimal.rst index ebb18bb..3495241 100644 --- a/Doc/library/decimal.rst +++ b/Doc/library/decimal.rst @@ -1294,8 +1294,8 @@ The behavior of Python's comparison operators can be a little surprising where a :const:`NaN` is involved. A test for equality where one of the operands is a quiet or signaling :const:`NaN` always returns :const:`False` (even when doing ``Decimal('NaN')==Decimal('NaN')``), while a test for inequality always returns -:const:`True`. An attempt to compare two Decimals using any of the :const:'<', -:const:'<=', :const:'>' or :const:'>=' operators will raise the +:const:`True`. An attempt to compare two Decimals using any of the ``<``, +``<=``, ``>`` or ``>=`` operators will raise the :exc:`InvalidOperation` signal if either operand is a :const:`NaN`, and return :const:`False` if this signal is trapped. Note that the General Decimal Arithmetic specification does not specify the behavior of direct comparisons; -- cgit v0.12