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 serhiy.storchaka
Recipients mark.dickinson, serhiy.storchaka, skrah
Date 2012-05-04.19:29:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1336159938.2329.69.camel@raxxla>
In-reply-to <1336155128.66.0.312689622467.issue14722@psf.upfronthosting.co.za>
Content
Here is a patch with tests.

> Nope.  Values just larger than DBL_MAX won't raise OverflowError here.

Isn't that a little bit. But values that rounded to DBL_MAX can raise
OverflowError. In any case it's too difficult to achieve strict behavior
in this corner case.

> Possibly.  But there's also the fact that 3.2 already returns inf here;  we'd need a pretty good reason to break that.

In the end, we may add the environment variable
PYTHONDONTRAISEEXCEPTIONIFFLOATOVERFLOWS to control this behaviour.

> Like I said, I'm not sure which the right way to go here is.

Take a look at the tests and may be you'll see the system.
Files
File name Uploaded
getargs_float_overflow_2.patch serhiy.storchaka, 2012-05-04.19:29:49
History
Date User Action Args
2012-05-04 19:29:51serhiy.storchakasetrecipients: + serhiy.storchaka, mark.dickinson, skrah
2012-05-04 19:29:50serhiy.storchakalinkissue14722 messages
2012-05-04 19:29:50serhiy.storchakacreate