Mark Dickinson added the comment:
This isn't a bug in Python: it's an unavoidable symptom of using binary
floating-point arithmetic internally to store values.
I recommend looking at the last chapter of the Python tutorial, which gives a
very nice explanation of floating-point issues.
http:
New submission from Aleš Drinovec :
*** Python 3.1.2rc1 (r312rc1:78742, Mar 7 2010, 07:49:40) [MSC v.1500 32 bit
(Intel)] on win32. ***
>>> 5.1+3.8
8.899
>>> 4.1+4.8
8.899
>>>
Tested in IDLE and in PyScripter
--
components: Interpreter Core
messages: 100842
no
