This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients DhaReaL, mark.dickinson
Date 2010-01-14.20:54:25
SpamBayes Score 2.05977e-05
Marked as misclassified No
Message-id <1263502467.65.0.981616625728.issue7704@psf.upfronthosting.co.za>
In-reply-to
Content
This is not a bug:  Python, like many other computer languages, stores floats in binary.  The values 1.6 and 0.6 aren't exactly representable in the internal format used, so the stored versions of 1.6 and 0.6 are actually just very close approximations to those values.  It just so happens that the approximation for 1.6 is a tiny amount larger than 1.6 (the exact value stored is 1.600000000000000088817841970012523233890533447265625), while the approximation for 0.6 is a tiny amount smaller than 0.6 (the exact value is 0.59999999999999997779553950749686919152736663818359375).

I recommend looking at the appendix to the Python tutorial for more information about floating point:

http://docs.python.org/tutorial/floatingpoint.html
History
Date User Action Args
2010-01-14 20:54:27mark.dickinsonsetrecipients: + mark.dickinson, DhaReaL
2010-01-14 20:54:27mark.dickinsonsetmessageid: <1263502467.65.0.981616625728.issue7704@psf.upfronthosting.co.za>
2010-01-14 20:54:25mark.dickinsonlinkissue7704 messages
2010-01-14 20:54:25mark.dickinsoncreate