mirror of
https://github.com/python/cpython.git
synced 2025-10-02 05:12:23 +00:00
Merge remote-tracking branch 'upstream/3.11' into 3.11
This commit is contained in:
commit
bd769d7d91
1 changed files with 4 additions and 4 deletions
|
@ -1688,7 +1688,7 @@ to sockets.
|
||||||
much data, if any, was successfully sent.
|
much data, if any, was successfully sent.
|
||||||
|
|
||||||
.. versionchanged:: 3.5
|
.. versionchanged:: 3.5
|
||||||
The socket timeout is no more reset each time data is sent successfully.
|
The socket timeout is no longer reset each time data is sent successfully.
|
||||||
The socket timeout is now the maximum total duration to send all data.
|
The socket timeout is now the maximum total duration to send all data.
|
||||||
|
|
||||||
.. versionchanged:: 3.5
|
.. versionchanged:: 3.5
|
||||||
|
@ -1911,8 +1911,8 @@ can be changed by calling :func:`setdefaulttimeout`.
|
||||||
|
|
||||||
* In *non-blocking mode*, operations fail (with an error that is unfortunately
|
* In *non-blocking mode*, operations fail (with an error that is unfortunately
|
||||||
system-dependent) if they cannot be completed immediately: functions from the
|
system-dependent) if they cannot be completed immediately: functions from the
|
||||||
:mod:`select` can be used to know when and whether a socket is available for
|
:mod:`select` module can be used to know when and whether a socket is available
|
||||||
reading or writing.
|
for reading or writing.
|
||||||
|
|
||||||
* In *timeout mode*, operations fail if they cannot be completed within the
|
* In *timeout mode*, operations fail if they cannot be completed within the
|
||||||
timeout specified for the socket (they raise a :exc:`timeout` exception)
|
timeout specified for the socket (they raise a :exc:`timeout` exception)
|
||||||
|
@ -2101,7 +2101,7 @@ manager protocol instead, open a socket with::
|
||||||
socket.socket(socket.AF_CAN, socket.SOCK_DGRAM, socket.CAN_BCM)
|
socket.socket(socket.AF_CAN, socket.SOCK_DGRAM, socket.CAN_BCM)
|
||||||
|
|
||||||
After binding (:const:`CAN_RAW`) or connecting (:const:`CAN_BCM`) the socket, you
|
After binding (:const:`CAN_RAW`) or connecting (:const:`CAN_BCM`) the socket, you
|
||||||
can use the :meth:`socket.send`, and the :meth:`socket.recv` operations (and
|
can use the :meth:`socket.send` and :meth:`socket.recv` operations (and
|
||||||
their counterparts) on the socket object as usual.
|
their counterparts) on the socket object as usual.
|
||||||
|
|
||||||
This last example might require special privileges::
|
This last example might require special privileges::
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue