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 bar.harel
Recipients David MacIver, bar.harel, steven.daprano
Date 2015-09-19.13:23:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442669001.54.0.513485246346.issue25177@psf.upfronthosting.co.za>
In-reply-to
Content
I believe it's an intended behavior as python's float has a limit after all. It's hard to reach it but definitely possible.
A workaround is to internally use Decimal (also take the advantage that it's implementation is now way faster) but it will cause a precision loss, and somewhat unexpected behavior.
Last thing we can do is catch that OverflowError and raise StatisticsError from exc.
I believe catching and re-raising as Statistics or just writing that it may also cause an Overflow error are the most viable ways.
Either way, I'd like another opinion before implementing either method as a patch.
History
Date User Action Args
2015-09-19 13:23:21bar.harelsetrecipients: + bar.harel, steven.daprano, David MacIver
2015-09-19 13:23:21bar.harelsetmessageid: <1442669001.54.0.513485246346.issue25177@psf.upfronthosting.co.za>
2015-09-19 13:23:21bar.harellinkissue25177 messages
2015-09-19 13:23:21bar.harelcreate