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 christian.heimes, marco.buttu, mark.dickinson, terry.reedy
Date 2013-07-30.07:47:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I think we might be better with two consistently behaving float classes

That sounds a bit extreme.  Personally, I'd look for a solution involving only one float class and a "with float.nonstopmode: ..." setting under which we get infinities and nans as prescribed by IEEE 754;  the default would be to produce exceptions in places where IEEE 754 would signal a floating-point exception (any of divide-by-zero, overflow or invalid-operation, but not for inexact or underflow).  This is definitely PEP territory, though;  and someone needs to undertake to implement it, which is distinctly nontrivial.

For this issue, I'd avoid making any small changes to current behaviour without having at least a clear vision set out of where we want to end up.
Date User Action Args
2013-07-30 07:47:59mark.dickinsonsetrecipients: + mark.dickinson, terry.reedy, christian.heimes, marco.buttu
2013-07-30 07:47:59mark.dickinsonsetmessageid: <>
2013-07-30 07:47:59mark.dickinsonlinkissue18570 messages
2013-07-30 07:47:58mark.dickinsoncreate