Issue #22063: Mention in asyncio documentation that socket operations require
the socket to be non-blocking
diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst
index b44fe75..1e16b9e 100644
--- a/Doc/library/asyncio-eventloop.rst
+++ b/Doc/library/asyncio-eventloop.rst
@@ -337,6 +337,8 @@
representing the data received. The maximum amount of data to be received
at once is specified by *nbytes*.
+ The socket *sock* must be non-blocking.
+
This method is a :ref:`coroutine <coroutine>`.
.. seealso::
@@ -351,6 +353,8 @@
an exception is raised, and there is no way to determine how much data, if
any, was successfully processed by the receiving end of the connection.
+ The socket *sock* must be non-blocking.
+
This method is a :ref:`coroutine <coroutine>`.
.. seealso::
@@ -367,6 +371,8 @@
:py:data:`~socket.AF_INET` and :py:data:`~socket.AF_INET6` address families.
Use :meth:`getaddrinfo` to resolve the hostname asynchronously.
+ The socket *sock* must be non-blocking.
+
This method is a :ref:`coroutine <coroutine>`.
.. seealso::
@@ -384,6 +390,8 @@
and *address* is the address bound to the socket on the other end of the
connection.
+ The socket *sock* must be non-blocking.
+
This method is a :ref:`coroutine <coroutine>`.
.. seealso::