➜

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 asvetlov, casevh, ezio.melotti, loewis, mark.dickinson, rhettinger, skrah
Date 2012-11-15.09:30:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352971855.95.0.937690887119.issue16469@psf.upfronthosting.co.za>
In-reply-to
Content 
> I think consistent behavior between int() and Fraction() is valuable.

Agreed.  If no-one objects I'll fix the Decimal -> Fraction and float -> Fraction conversions to match what Decimal -> int and float -> int currently do (ValueError and OverflowError).

Then we can open a new issue to discuss having infinities give ValueError versus OverflowError for all four cases of {float, Decimal} -> {int, Fraction}.
History
Date User Action Args
2012-11-15 09:30:56mark.dickinsonsetrecipients: + mark.dickinson, loewis, rhettinger, casevh, ezio.melotti, asvetlov, skrah
2012-11-15 09:30:55mark.dickinsonsetmessageid: <1352971855.95.0.937690887119.issue16469@psf.upfronthosting.co.za>
2012-11-15 09:30:55mark.dickinsonlinkissue16469 messages
2012-11-15 09:30:55mark.dickinsoncreate