8

I try get ration of variable and get unexpected result. Can somebody explain this?

>>> value = 3.2
>>> ratios = value.as_integer_ratio()
>>> ratios
(3602879701896397, 1125899906842624)
>>> ratios[0] / ratios[1]
3.2

I using python 3.3

But I think that (16, 5) is much better solution

And why it correct for 2.5

>>> value = 2.5
>>> value.as_integer_ratio()
(5, 2)
Bhargav Rao
  • 45,811
  • 27
  • 120
  • 136
itdxer
  • 1,206
  • 1
  • 12
  • 38

2 Answers2

18

Use the fractions module to simplify fractions:

>>> from fractions import Fraction
>>> Fraction(3.2)
Fraction(3602879701896397, 1125899906842624)
>>> Fraction(3.2).limit_denominator()
Fraction(16, 5)

From the Fraction.limit_denominator() function:

Finds and returns the closest Fraction to self that has denominator at most max_denominator. This method is useful for finding rational approximations to a given floating-point number

Floating point numbers are limited in precision and cannot represent many numbers exactly; what you see is a rounded representation, but the real number is:

>>> format(3.2, '.50f')
'3.20000000000000017763568394002504646778106689453125'

because a floating point number is represented as a sum of binary fractions; 1/5 can only be represented by adding up 1/8 + 1/16 + 1/128 + more binary fractions for increasing exponents of two.

Martijn Pieters
  • 963,270
  • 265
  • 3,804
  • 3,187
5

It's not 16/5 because 3.2 isn't 3.2 exactly... it's a floating point rough approximation of it... eg: 3.20000000000000017764

Jon Clements
  • 132,101
  • 31
  • 237
  • 267
  • But why `2.5` the same as `2.5` and `3.2` not the same? – itdxer Nov 21 '13 at 15:12
  • @itdxer I think it's value is pretty stable for numbers with `.5` as a divisor. They can be represented exactly as you define them. – aIKid Nov 21 '13 at 15:14
  • @itdxer because some numbers can be represented exactly and some can't... See the link that [FallenAngel provided](http://stackoverflow.com/questions/2100490/floating-point-inaccuracy-examples) – Jon Clements Nov 21 '13 at 15:15
  • 1
    Because you can display integers with binary (base 2) but displaying decimal part is hard because you may not exactly write a decimal number in binary (base 2). So programming languages tries to evaluate the value closest to your expected result. – FallenAngel Nov 21 '13 at 15:16