summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorendolith <endolith@gmail.com>2015-03-09 22:57:36 -0400
committerendolith <endolith@gmail.com>2015-03-09 22:57:36 -0400
commit0784049118233ef7b087308a5e7bfc638085b7a4 (patch)
tree594458ea53852df69df52e4048ece0c57417f2e6 /doc
parent82c03c24f1dd40efc9b9b00783035898c6eacdfb (diff)
downloadnumpy-0784049118233ef7b087308a5e7bfc638085b7a4.tar.gz
DOC: adjust wording of random data note
Diffstat (limited to 'doc')
-rw-r--r--doc/TESTS.rst.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/TESTS.rst.txt b/doc/TESTS.rst.txt
index 876f37bc5..690baca3d 100644
--- a/doc/TESTS.rst.txt
+++ b/doc/TESTS.rst.txt
@@ -378,9 +378,9 @@ failing tests are marked as ``'K'`` (or ``'KNOWN'`` if ``verbose >
Tests on random data
--------------------
-Tests on random data are good, but since test failures are meant to
-expose new bugs or regressions, a test that passes most of the time
-but fails occasionally with no code changes is not helpful.
-Make the random data deterministic by setting the random number seed
-before generating it. Either Python's ``random.seed()`` or Numpy's
-``numpy.random.seed()``, depending on the source of random numbers.
+Tests on random data are good, but since test failures are meant to expose
+new bugs or regressions, a test that passes most of the time but fails
+occasionally with no code changes is not helpful. Make the random data
+deterministic by setting the random number seed before generating it. Use
+either Python's ``random.seed(some_number)`` or Numpy's
+``numpy.random.seed(some_number)``, depending on the source of random numbers.