Message320394
| Author | tim.peters |
|---|---|
| Recipients | Serge Anuchin, mark.dickinson, pitrou, r.david.murray, rhettinger, serhiy.storchaka, skrah, steven.daprano, tim.peters, vstinner |
| Date | 2018-06-25.01:38:31 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1529890712.2.0.56676864532.issue24567@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
There are a couple bug reports here that have been open for years, and it's about time we closed them. My stance: if any platform still exists on which "double rounding" is still a potential problem, Python _configuration_ should be changed to disable double rounding on such platforms (there's usually a C compiler flag that can make this happen, but even if there isn't a couple lines of inline assembler could be added at Python startup to set the Pentium's FPU "precision control" bits to "round to 53 bits" mode). `random` is a red herring here! We don't want gratuitously different results across 754 boxes in any operations. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-06-25 01:38:32 | tim.peters | set | recipients: + tim.peters, rhettinger, mark.dickinson, pitrou, vstinner, steven.daprano, r.david.murray, skrah, serhiy.storchaka, Serge Anuchin |
| 2018-06-25 01:38:32 | tim.peters | set | messageid: <1529890712.2.0.56676864532.issue24567@psf.upfronthosting.co.za> |
| 2018-06-25 01:38:32 | tim.peters | link | issue24567 messages |
| 2018-06-25 01:38:31 | tim.peters | create | |