bpo-31736: Fix typos in PEP 485

Reported by Ben Bolker.
This commit is contained in:
Berker Peksag 2017-10-10 08:26:27 +03:00 committed by GitHub
parent 858f82d1b8
commit 070dc7e037
1 changed files with 2 additions and 2 deletions

View File

@ -427,7 +427,7 @@ yield the same result, and it is also about half of the precision
available to a python float. In the general case, a good numerical available to a python float. In the general case, a good numerical
algorithm is not expected to lose more than about half of available algorithm is not expected to lose more than about half of available
digits of accuracy, and if a much larger tolerance is acceptable, the digits of accuracy, and if a much larger tolerance is acceptable, the
user should be considering the proper value in that case. Thus 1-e9 is user should be considering the proper value in that case. Thus 1e-9 is
expected to "just work" for many cases. expected to "just work" for many cases.
Absolute tolerance default Absolute tolerance default
@ -447,7 +447,7 @@ appropriate value.
It was suggested that comparing to zero is, in fact, a common use case It was suggested that comparing to zero is, in fact, a common use case
(evidence suggest that the numpy functions are often used with zero). (evidence suggest that the numpy functions are often used with zero).
In this case, it would be desirable to have a "useful" default. Values In this case, it would be desirable to have a "useful" default. Values
around 1-e8 were suggested, being about half of floating point around 1e-8 were suggested, being about half of floating point
precision for values of around value 1. precision for values of around value 1.
However, to quote The Zen: "In the face of ambiguity, refuse the However, to quote The Zen: "In the face of ambiguity, refuse the