summaryrefslogtreecommitdiffstats
path: root/Include/internal
diff options
context:
space:
mode:
authorRishi <rishi_devan@mail.com>2021-06-01 21:30:05 (GMT)
committerGitHub <noreply@github.com>2021-06-01 21:30:05 (GMT)
commitfcda0f508ead26581a77108de19b278c4d062dc4 (patch)
tree12a692f98a164a15e200baca80034fbf44ab466d /Include/internal
parent87272b70f157af76cb14ff90d73dfc5d9bfb945a (diff)
downloadcpython-fcda0f508ead26581a77108de19b278c4d062dc4.zip
cpython-fcda0f508ead26581a77108de19b278c4d062dc4.tar.gz
cpython-fcda0f508ead26581a77108de19b278c4d062dc4.tar.bz2
Fix typo in block comment in Include/internal/pycore_condvar.h (GH-26457)
Diffstat (limited to 'Include/internal')
-rw-r--r--Include/internal/pycore_condvar.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/Include/internal/pycore_condvar.h b/Include/internal/pycore_condvar.h
index 8b89d70..edb7dc8 100644
--- a/Include/internal/pycore_condvar.h
+++ b/Include/internal/pycore_condvar.h
@@ -60,7 +60,7 @@ typedef CRITICAL_SECTION PyMUTEX_T;
with a Semaphore.
Semaphores are available on Windows XP (2003 server) and later.
We use a Semaphore rather than an auto-reset event, because although
- an auto-resent event might appear to solve the lost-wakeup bug (race
+ an auto-reset event might appear to solve the lost-wakeup bug (race
condition between releasing the outer lock and waiting) because it
maintains state even though a wait hasn't happened, there is still
a lost wakeup problem if more than one thread are interrupted in the