Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

Issue #22063: Mention in asyncio documentation that socket operations require 

the socket to be non-blocking
This commit is contained in:
Victor Stinner 2014-07-29 23:12:22 +02:00
parent 9c9f1f10d3
commit ec2ce092a2
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Doc/library/asyncio-eventloop.rst
View File

@ -337,6 +337,8 @@ Low-level socket operations
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 @@ Low-level socket operations
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 @@ Low-level socket operations
: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 @@ Low-level socket operations
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::