[issue35590] logging.handlers.SysLogHandler with STREAM connects in constructor without timeout

Change by Irit Katriel : -- nosy: +vinay.sajip versions: +Python 3.11 -Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker ___ __

[issue35590] logging.handlers.SysLogHandler with STREAM connects in constructor without timeout

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 default time

[issue35590] logging.handlers.SysLogHandler with STREAM connects in constructor without timeout

Change by Emmanuel Arias : -- components: +Library (Lib) type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue35590] logging.handlers.SysLogHandler with STREAM connects in constructor without timeout

Emmanuel Arias added the comment: Hi, If I don't see bad, if a timeout occur this is catch by the OSError exception. -- nosy: +eamanu ___ Python tracker ___

[issue35590] logging.handlers.SysLogHandler with STREAM connects in constructor without timeout

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 s