random.gauss() uses a piece of hidden state used by nothing else,
and the .seed() and .whseed() methods failed to reset it. In other
words, setting the seed didn't completely determine the sequence of
results produced by random.gauss(). It does now. Programs repeatedly
mixing calls to a seed method with calls to gauss() may see different
results now.
Bugfix candidate (random.gauss() has always been broken in this way),
despite that it may change results.
diff --git a/Lib/random.py b/Lib/random.py
index f502d1d..fe25642 100644
--- a/Lib/random.py
+++ b/Lib/random.py
@@ -116,7 +116,6 @@
"""
self.seed(x)
- self.gauss_next = None
## -------------------- core generator -------------------
@@ -150,6 +149,8 @@
a, z = divmod(a, 30322)
self._seed = int(x)+1, int(y)+1, int(z)+1
+ self.gauss_next = None
+
def random(self):
"""Get the next random number in the range [0.0, 1.0)."""
@@ -238,6 +239,8 @@
# Zero is a poor seed, so substitute 1
self._seed = (x or 1, y or 1, z or 1)
+ self.gauss_next = None
+
def whseed(self, a=None):
"""Seed from hashable object's hash code.