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 tim.peters
Recipients Serge Anuchin, mark.dickinson, pitrou, r.david.murray, rhettinger, serhiy.storchaka, skrah, steven.daprano, tim.peters, vstinner
Date 2015-07-10.14:49:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1436539797.63.0.141274062786.issue24567@psf.upfronthosting.co.za>
In-reply-to
Content
> Anyway, if we modify random.py, the generated
> numbers should be different, no?

Not in a bugfix release.  The `min()` trick changes no results whatsoever on a box that doesn't do double-rounding.

On a box that does do double-rounding, the only difference in results is that the `min()` trick stops a nasty exception in a relative handful of cases (& makes no difference to any case in which that exception isn't raised).

The sequence of results may be different on platforms with double-rounding and without double-rounding, but that's always been true.  The `min()` trick changes nothing about that either, except to prevent unintended exceptions on double-rounding boxes.

Note that switching to use SSE2 instead also changes nothing on boxes that don't do double-rounding.  It would change some results (beyond _just_ stopping bogus exceptions) on boxes that do double-rounding.
History
Date User Action Args
2015-07-10 14:49:57tim.peterssetrecipients: + tim.peters, rhettinger, mark.dickinson, pitrou, vstinner, steven.daprano, r.david.murray, skrah, serhiy.storchaka, Serge Anuchin
2015-07-10 14:49:57tim.peterssetmessageid: <1436539797.63.0.141274062786.issue24567@psf.upfronthosting.co.za>
2015-07-10 14:49:57tim.peterslinkissue24567 messages
2015-07-10 14:49:57tim.peterscreate