jso2460 added the comment:
Yes, when timeout occurs it's then caught by the OSError -- you are completely
right about that.
Instead my suggestion was meant to provide an option to specify a timeout when
creating an instance of SysLogHandler. Currently the socket is created with
de
New submission from jso2460 :
logging.handlers.SysLogHandler in __init__ contains the following code, where
socket is created and then connected right away. This seem to provide no way to
specify a connection timeout for the socket being created.
sock = socket.socket(af, socktype, proto)
if
