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 tim.peters
Recipients Nofar Schnider, gvanrossum, rhettinger, tim.peters
Date 2018-03-13.21:36:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Is this also desired for fractions.Fraction and numbers.Rational?

I think so.  The idea, e.g., that "it's obvious" for Fraction is no more compelling than that it's even more obvious for ints ;-)  Given that it's spreading to ints anyway, there's an opportunity to make it possible for clients to write utterly uniform code for every type whose values can be represented as integer ratios.

I'd also say it's desirable to extend the Fraction constructor, to accept argument(s) of any type(s) that implement as_integer_ratio().  But that should probably be a different issue.
Date User Action Args
2018-03-13 21:36:37tim.peterssetrecipients: + tim.peters, gvanrossum, rhettinger, Nofar Schnider
2018-03-13 21:36:37tim.peterssetmessageid: <>
2018-03-13 21:36:37tim.peterslinkissue33073 messages
2018-03-13 21:36:37tim.peterscreate