On Wed, 2019-04-03 at 22:58 +0100, Gordon Sim wrote: > ... > I think the issue is that the loss of the socket no longer results in > a > transport_close event? (or that the socket.error is raised and > causes > the loop to exit before processing that event?)
Hmm, I think that in the case of a connect call failing there never was a transport to generate the transport_close event in the first place - the python code whch fails the connect doesn't generate that event. A --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
