Minor formatting fixes to PEP 485, missed in the first pass
This commit is contained in:
parent
6c5d998ce0
commit
79268209af
20
pep-0485.txt
20
pep-0485.txt
|
@ -103,14 +103,14 @@ theory, it should work for any type that supports ``abs()``,
|
|||
comparisons, and subtraction. The code will be written and tested to
|
||||
accommodate these types:
|
||||
|
||||
* ``Decimal``
|
||||
* ``Decimal``
|
||||
|
||||
* ``int``
|
||||
* ``int``
|
||||
|
||||
* ``Fraction``
|
||||
* ``Fraction``
|
||||
|
||||
* ``complex``: for complex, ``abs(z)`` will be used for scaling and
|
||||
comparison.
|
||||
* ``complex``: for complex, ``abs(z)`` will be used for scaling and
|
||||
comparison.
|
||||
|
||||
|
||||
Behavior near zero
|
||||
|
@ -134,7 +134,7 @@ Relative Difference
|
|||
===================
|
||||
|
||||
There are essentially two ways to think about how close two numbers
|
||||
are to each-other: absolute difference: simple ``abs(a-b)``, and
|
||||
are to each-other: absolute difference: simply ``abs(a-b)``, and
|
||||
relative difference: ``abs(a-b)/scale_factor`` [2]_. The absolute
|
||||
difference is trivial enough that this proposal focuses on the
|
||||
relative difference.
|
||||
|
@ -142,13 +142,13 @@ relative difference.
|
|||
Usually, the scale factor is some function of the values under
|
||||
consideration, for instance:
|
||||
|
||||
1) The absolute value of one of the input values
|
||||
1) The absolute value of one of the input values
|
||||
|
||||
2) The maximum absolute value of the two
|
||||
2) The maximum absolute value of the two
|
||||
|
||||
3) The minimum absolute value of the two.
|
||||
3) The minimum absolute value of the two.
|
||||
|
||||
4) The arithmetic mean of the two
|
||||
4) The arithmetic mean of the two
|
||||
|
||||
|
||||
Symmetry
|
||||
|
|
Loading…
Reference in New Issue