Fix typo in test module usage message (GH-11374)

https://github.com/python/cpython/commit/75bf2b1e23ee7672fccb1e0fa23d6113cc3... commit: 75bf2b1e23ee7672fccb1e0fa23d6113cc3d38d7 branch: 3.7 author: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> committer: GitHub <noreply@github.com> date: 2018-12-30T21:59:08-08:00 summary: 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 (cherry picked from commit 7108aab49c2b6d6d81766c354f9a809278e03d4c) Co-authored-by: sth <sth.dev@tejp.de> files: M Lib/test/libregrtest/cmdline.py diff --git a/Lib/test/libregrtest/cmdline.py b/Lib/test/libregrtest/cmdline.py index 09270323611f..7cd85bf2803a 100644 --- a/Lib/test/libregrtest/cmdline.py +++ b/Lib/test/libregrtest/cmdline.py @@ -68,7 +68,7 @@ 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
participants (1)
-
Miss Islington (bot)