docs/usocket: Clarify that socket timeout raises OSError exception.
This commit is contained in:
parent
ef1bbada96
commit
a1a8f01799
@ -149,10 +149,18 @@ Methods
|
|||||||
|
|
||||||
Set a timeout on blocking socket operations. The value argument can be a nonnegative floating
|
Set a timeout on blocking socket operations. The value argument can be a nonnegative floating
|
||||||
point number expressing seconds, or None. If a non-zero value is given, subsequent socket operations
|
point number expressing seconds, or None. If a non-zero value is given, subsequent socket operations
|
||||||
will raise a timeout exception if the timeout period value has elapsed before the operation has
|
will raise an ``OSError`` exception if the timeout period value has elapsed before the operation has
|
||||||
completed. If zero is given, the socket is put in non-blocking mode. If None is given, the socket
|
completed. If zero is given, the socket is put in non-blocking mode. If None is given, the socket
|
||||||
is put in blocking mode.
|
is put in blocking mode.
|
||||||
|
|
||||||
|
.. admonition:: Difference to CPython
|
||||||
|
:class: attention
|
||||||
|
|
||||||
|
CPython raises a ``socket.timeout`` exception in case of timeout,
|
||||||
|
which is an ``OSError`` subclass. MicroPython raises an OSError directly
|
||||||
|
instead. If you use ``except OSError:`` to catch the exception,
|
||||||
|
your code will work both in MicroPython and CPython.
|
||||||
|
|
||||||
.. method:: socket.setblocking(flag)
|
.. method:: socket.setblocking(flag)
|
||||||
|
|
||||||
Set blocking or non-blocking mode of the socket: if flag is false, the socket is set to non-blocking,
|
Set blocking or non-blocking mode of the socket: if flag is false, the socket is set to non-blocking,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user