Zbyszek Szmek <zbys...@in.waw.pl> added the comment: [part mangled by the tracker]
"> 1.1999999999999999555910790149937383830547332763671875 "> "> which is accurate to around 16 decimal digits.) It is easy to count, that exactly 17 digits are accurate. I have to admit, that I'm completely lost here --- why would a vastly inaccurate number (with more than half of digits wrong) be ever stored? If "1.2" is converted to a float (a C double in current implementation), it has 15.96 decimal digits of precision. " > Similarly, the result of any " > floating-point operation must often be rounded to fit into the " > internal format, resulting in another tiny error. "Similarly, the result of a floating-point operation must be rounded to fit into the fixed precision, often resulting in another tiny error." ? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14245> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
