summaryrefslogtreecommitdiffstats
path: root/Lib
diff options
context:
space:
mode:
authorsth <sth.dev@tejp.de>2018-12-31 05:41:39 (GMT)
committerMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2018-12-31 05:41:39 (GMT)
commit7108aab49c2b6d6d81766c354f9a809278e03d4c (patch)
tree80a14046023fedb7f1b3e7c92d19a3359bb60990 /Lib
parentb539cef31c060c7eecc331d25a23b80ded0baf08 (diff)
downloadcpython-7108aab49c2b6d6d81766c354f9a809278e03d4c.zip
cpython-7108aab49c2b6d6d81766c354f9a809278e03d4c.tar.gz
cpython-7108aab49c2b6d6d81766c354f9a809278e03d4c.tar.bz2
Fix typo in test module usage message (GH-11374)
A minor typo in the output of `python -m test -h`. A space was missing in between two words. howmuch -> how much
Diffstat (limited to 'Lib')
-rw-r--r--Lib/test/libregrtest/cmdline.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/Lib/test/libregrtest/cmdline.py b/Lib/test/libregrtest/cmdline.py
index 0927032..7cd85bf 100644
--- a/Lib/test/libregrtest/cmdline.py
+++ b/Lib/test/libregrtest/cmdline.py
@@ -68,7 +68,7 @@ typically try to ascertain containers keep working when containing more than
2 billion objects, which only works on 64-bit systems. There are also some
tests that try to exhaust the address space of the process, which only makes
sense on 32-bit systems with at least 2Gb of memory. The passed-in memlimit,
-which is a string in the form of '2.5Gb', determines howmuch memory the
+which is a string in the form of '2.5Gb', determines how much memory the
tests will limit themselves to (but they may go slightly over.) The number
shouldn't be more memory than the machine has (including swap memory). You
should also keep in mind that swap memory is generally much, much slower