diff options
author | Georg Brandl <georg@python.org> | 2014-10-06 15:51:09 (GMT) |
---|---|---|
committer | Georg Brandl <georg@python.org> | 2014-10-06 15:51:09 (GMT) |
commit | 9205e9ebdc3440cfdcf557e807dc693c3d226f61 (patch) | |
tree | a97649e853f6c4b4f5ecc80f4bed5a950a5e761c /Doc/faq/design.rst | |
parent | 7fa4a8f15a812a630aa764de584efbe5242c9bb3 (diff) | |
download | cpython-9205e9ebdc3440cfdcf557e807dc693c3d226f61.zip cpython-9205e9ebdc3440cfdcf557e807dc693c3d226f61.tar.gz cpython-9205e9ebdc3440cfdcf557e807dc693c3d226f61.tar.bz2 |
Closes #16155: fix a few errors in doctest output of the FAQ pages.
Diffstat (limited to 'Doc/faq/design.rst')
-rw-r--r-- | Doc/faq/design.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/faq/design.rst b/Doc/faq/design.rst index d7be299..151bcde 100644 --- a/Doc/faq/design.rst +++ b/Doc/faq/design.rst @@ -49,7 +49,7 @@ Why are floating-point calculations so inaccurate? Users are often surprised by results like this:: >>> 1.2 - 1.0 - 0.199999999999999996 + 0.19999999999999996 and think it is a bug in Python. It's not. This has little to do with Python, and much more to do with how the underlying platform handles floating-point |