[3.12] Link to correct class methods in asyncio primitives docs (GH-127270) #127438
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(cherry picked from commit 15d6506)
Co-authored-by: Ollanta Cuba Gyllensten [email protected]
@kumaraditya303
I've checked that
wait_for
does indeed callwait()
before checking the predicate but I'd like to know whether this additional paragraph forwait
is needed or not:Note
Note that a task may return from this call spuriously,
which is why the caller should always re-check the state
and be prepared to :meth:
~Condition.wait
again. For this reason, you mayprefer to use :meth:
~Condition.wait_for
instead.📚 Documentation preview 📚: https://cpython-previews--127438.org.readthedocs.build/