diff options
author | Géry Ogam <gery.ogam@gmail.com> | 2019-05-17 22:44:57 (GMT) |
---|---|---|
committer | Cheryl Sabella <cheryl.sabella@gmail.com> | 2019-05-17 22:44:57 (GMT) |
commit | 51a860ee01a9e96f8013fe6ca836ec95e7eb3010 (patch) | |
tree | c16c77d031ee2b068c14d210055ab846f6499206 /Doc | |
parent | b594784272d4907b1c40d3c40d17cb081aa9cf9b (diff) | |
download | cpython-51a860ee01a9e96f8013fe6ca836ec95e7eb3010.zip cpython-51a860ee01a9e96f8013fe6ca836ec95e7eb3010.tar.gz cpython-51a860ee01a9e96f8013fe6ca836ec95e7eb3010.tar.bz2 |
Correct typos in the Barrier specification (GH-9395)
Diffstat (limited to 'Doc')
-rw-r--r-- | Doc/library/threading.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/library/threading.rst b/Doc/library/threading.rst index 99dd7ff..715940c 100644 --- a/Doc/library/threading.rst +++ b/Doc/library/threading.rst @@ -968,7 +968,7 @@ As an example, here is a simple way to synchronize a client and server thread:: Return the barrier to the default, empty state. Any threads waiting on it will receive the :class:`BrokenBarrierError` exception. - Note that using this function may can require some external + Note that using this function may require some external synchronization if there are other threads whose state is unknown. If a barrier is broken it may be better to just leave it and create a new one. @@ -976,7 +976,7 @@ As an example, here is a simple way to synchronize a client and server thread:: Put the barrier into a broken state. This causes any active or future calls to :meth:`wait` to fail with the :class:`BrokenBarrierError`. Use - this for example if one of the needs to abort, to avoid deadlocking the + this for example if one of the threads needs to abort, to avoid deadlocking the application. It may be preferable to simply create the barrier with a sensible |