diff options
| author | Antoine Pitrou <solipsis@pitrou.net> | 2012-04-11 17:37:56 (GMT) |
|---|---|---|
| committer | Antoine Pitrou <solipsis@pitrou.net> | 2012-04-11 17:37:56 (GMT) |
| commit | f6cd9b2d46ca5701a20a9cecbe8aba7ae9cc21bd (patch) | |
| tree | 1842eaf31e2104288e5f0bde7e3412925bbfcf89 /Doc | |
| parent | 2c5807572f34627c5adf5a10559a82d904cca543 (diff) | |
| download | cpython-f6cd9b2d46ca5701a20a9cecbe8aba7ae9cc21bd.zip cpython-f6cd9b2d46ca5701a20a9cecbe8aba7ae9cc21bd.tar.gz cpython-f6cd9b2d46ca5701a20a9cecbe8aba7ae9cc21bd.tar.bz2 | |
Improve the threading.Condition docs.
Diffstat (limited to 'Doc')
| -rw-r--r-- | Doc/library/threading.rst | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/Doc/library/threading.rst b/Doc/library/threading.rst index 8571104..30f7ece 100644 --- a/Doc/library/threading.rst +++ b/Doc/library/threading.rst @@ -561,12 +561,14 @@ producer-consumer situation with unlimited buffer capacity:: # Produce one item with cv: make_an_item_available() + cv.notify() The ``while`` loop checking for the application's condition is necessary because :meth:`~Condition.wait` can return after an arbitrary long time, -and other threads may have exhausted the available items in between. This -is inherent to multi-threaded programming. The :meth:`~Condition.wait_for` -method can be used to automate the condition checking:: +and the condition which prompted the :meth:`~Condition.notify` call may +no longer hold true. This is inherent to multi-threaded programming. The +:meth:`~Condition.wait_for` method can be used to automate the condition +checking, and eases the computation of timeouts:: # Consume an item with cv: |