summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2019-10-10 21:01:33 -0700
committerNed Deily <nad@python.org>2019-10-14 17:19:12 -0400
commit49d7428c26d4e9211d14585ca8b421a2582d6366 (patch)
tree7e6ba160b742c812e9a373240730c7b9374faac5
parentbpo-32996: Documentation fix-up. (GH-16646) (diff)
downloadcpython-49d7428c26d4e9211d14585ca8b421a2582d6366.tar.gz
cpython-49d7428c26d4e9211d14585ca8b421a2582d6366.tar.bz2
cpython-49d7428c26d4e9211d14585ca8b421a2582d6366.zip
Typo fix: "throuhgh" should be "through". (GH-16704)
(cherry picked from commit a8e0d3141e271b3c0fbb7399a911f0c3aa567e30) Co-authored-by: Hansraj Das <raj.das.136@gmail.com>
-rw-r--r--Python/condvar.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/Python/condvar.h b/Python/condvar.h
index 951b8ad47f0..802d53fbe69 100644
--- a/Python/condvar.h
+++ b/Python/condvar.h
@@ -194,7 +194,7 @@ _PyCOND_WAIT_MS(PyCOND_T *cv, PyMUTEX_T *cs, DWORD ms)
* just means an extra spurious wakeup for a waiting thread.
* ('waiting' corresponds to the semaphore's "negative" count and
* we may end up with e.g. (waiting == -1 && sem.count == 1). When
- * a new thread comes along, it will pass right throuhgh, having
+ * a new thread comes along, it will pass right through, having
* adjusted it to (waiting == 0 && sem.count == 0).
*/