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.

classification
Title: Unexpected Fraction.from_float() Behavior
Type: behavior Stage:
Components: Library (Lib) Versions: Python 3.1
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: bsidhom, r.david.murray
Priority: normal Keywords:

Created on 2010-09-11 05:06 by bsidhom, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg116076 - (view) Author: (bsidhom) Date: 2010-09-11 05:06
The Fractions.from_float() call returns an incorrect value when run on certain numbers. Some test runs have been listed below. Note that this problem does not exist when the same float is converted to a string and then passed to the standard Fraction() constructor; I do not know if this is an inherent problem due to the structure of the float itself or an implementation issue.

>>> for x in [1.23, 1.24, 1.25, 1.26, 1.27]:
	print(Fraction.from_float(x))
	print(Fraction(str(x)))

	
2769713770832855/2251799813685248
123/100
5584463537939415/4503599627370496
31/25
5/4
5/4
5674535530486825/4503599627370496
63/50
2859785763380265/2251799813685248
127/100

The problem does not exist if a string literal is passed either:

>>> print(Fraction('1.23'))
123/100
msg116096 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2010-09-11 14:00
Please read about floating point arithmetic in the tutorial:

   http://docs.python.org/tutorial/floatingpoint.html

Also observe that this works:

    >>> Fraction(Decimal('1.23'))
    Fraction(123, 100)

So yes, it is a limitation in how floating point is represented...in all languages and platforms that use binary floating point.
History
Date User Action Args
2022-04-11 14:57:06adminsetgithub: 54038
2010-09-11 14:00:03r.david.murraysetstatus: open -> closed

nosy: + r.david.murray
messages: + msg116096

resolution: not a bug
2010-09-11 05:06:24bsidhomcreate