Message251081
| Author | David MacIver |
|---|---|
| Recipients | David MacIver, bar.harel, steven.daprano |
| Date | 2015-09-19.13:58:54 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1442671134.19.0.649793467403.issue25177@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm not sure what you mean by float having a limit here. It's certainly finite precision, but there is still a representable value with that finite precision closest to the mean. As an example where there is an obvious correct answer that will trigger this error: statistics.mean([sys.float_info.max, sys.float_info.max]), this should return sys.float_info.max (which is definitely representable!), but instead raises this overflow error. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-09-19 13:58:54 | David MacIver | set | recipients: + David MacIver, steven.daprano, bar.harel |
| 2015-09-19 13:58:54 | David MacIver | set | messageid: <1442671134.19.0.649793467403.issue25177@psf.upfronthosting.co.za> |
| 2015-09-19 13:58:54 | David MacIver | link | issue25177 messages |
| 2015-09-19 13:58:54 | David MacIver | create | |