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 bsidhom
Recipients bsidhom
Date 2010-09-11.05:06:21
SpamBayes Score 5.3897446e-07
Marked as misclassified No
Message-id <1284181586.06.0.381689525187.issue9829@psf.upfronthosting.co.za>
In-reply-to
Content
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
History
Date User Action Args
2010-09-11 05:06:26bsidhomsetrecipients: + bsidhom
2010-09-11 05:06:26bsidhomsetmessageid: <1284181586.06.0.381689525187.issue9829@psf.upfronthosting.co.za>
2010-09-11 05:06:24bsidhomlinkissue9829 messages
2010-09-11 05:06:22bsidhomcreate