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 belopolsky, mark.dickinson, rhettinger, skrah
Date 2010-06-29.20:07:25
SpamBayes Score 2.3917375e-05
Marked as misclassified No
Message-id <1277842047.83.0.33124375772.issue8947@psf.upfronthosting.co.za>
In-reply-to
Content
After discussions on IRC, I'm going to close this as rejected.  Convergence of the float and Decimal APIs is a nice idea, but in this case it's not clear that it really works.  In particular, for duck typing to be sensible, int and Fraction would also have to grow an as_integer_ratio method.  And that seems a superfluous when those two types already have the same functionality in the form of .numerator and .denominator attributes.

I also agree with Raymond that we shouldn't be fattening the decimal API without good reason.

Alexander:  wouldn't conversion to Fraction solve the issue in this case?  The Fraction constructor accepts floats, Decimal instances and ints directly.
History
Date User Action Args
2010-06-29 20:07:28mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, belopolsky, skrah
2010-06-29 20:07:27mark.dickinsonsetmessageid: <1277842047.83.0.33124375772.issue8947@psf.upfronthosting.co.za>
2010-06-29 20:07:25mark.dickinsonlinkissue8947 messages
2010-06-29 20:07:25mark.dickinsoncreate