Changes by Christopher Gurnee <ch...@gurneeconsulting.net>:
--
nosy: +gurnec
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pytho
Christopher Gurnee added the comment:
Option 3 of course wasn't my first choice (given how small the patch is and how
minimal its potential negative impact), but it's certainly better than allowing
an issue to linger in limbo.
Thank you, all
Christopher Gurnee added the comment:
There's been no activity on this issue in a few months The three options as
I see it are:
1. Fix it for both randrange and SystemRandom.randrange, breaking randrange's
implied stability between minor versions.
2. Fix it only
Christopher Gurnee added the comment:
If you have to care about security, you shouldn't use the random module
at all. random.SystemRandom() merely uses a CPRNG as entropy source. But
It also manipulates numbers in ways that may or may not be safe.
I must respectfully disagree
New submission from Christopher Gurnee:
Due to an optimization in random.randrange() only in Python 2, as the
stop-start range approaches 2^53 the output becomes noticeably biased. This bug
also affects random.SystemRandom.
For example, counting the number of even ints in a set of 10^6 random
Christopher Gurnee added the comment:
I shouldn't have called this a rounding error issue, that's not really what it
is.
A smaller example might help.
If I'm given a random int, x, in the range [0, 12), and asked to produce from
it a random int, y, in the range (0,8], I've got (at least
