https://github.com/python/cpython/commit/15d6506d175780bb29e5fcde654e3860408aa93e
commit: 15d6506d175780bb29e5fcde654e3860408aa93e
branch: main
author: Ollanta Cuba Gyllensten <[email protected]>
committer: kumaraditya303 <[email protected]>
date: 2024-11-29T16:20:40Z
summary:

Link to correct class methods in asyncio primitives docs (#127270)

files:
M Doc/library/asyncio-sync.rst

diff --git a/Doc/library/asyncio-sync.rst b/Doc/library/asyncio-sync.rst
index 3cf8e2737e85dc..77c2e97da11990 100644
--- a/Doc/library/asyncio-sync.rst
+++ b/Doc/library/asyncio-sync.rst
@@ -259,8 +259,8 @@ Condition
 
       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:`wait` again. For this reason, you may
-      prefer to use :meth:`wait_for` instead.
+      and be prepared to :meth:`~Condition.wait` again. For this reason, you 
may
+      prefer to use :meth:`~Condition.wait_for` instead.
 
    .. coroutinemethod:: wait_for(predicate)
 
@@ -268,7 +268,7 @@ Condition
 
       The predicate must be a callable which result will be
       interpreted as a boolean value.  The method will repeatedly
-      :meth:`wait` until the predicate evaluates to *true*. The final value is 
the
+      :meth:`~Condition.wait` until the predicate evaluates to *true*. The 
final value is the
       return value.
 
 
@@ -434,7 +434,7 @@ Barrier
    .. coroutinemethod:: abort()
 
       Put the barrier into a broken state.  This causes any active or future
-      calls to :meth:`wait` to fail with the :class:`BrokenBarrierError`.
+      calls to :meth:`~Barrier.wait` to fail with the 
:class:`BrokenBarrierError`.
       Use this for example if one of the tasks needs to abort, to avoid 
infinite
       waiting tasks.
 

_______________________________________________
Python-checkins mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-checkins.python.org/
Member address: [email protected]

Reply via email to