[issue23333] asyncio: call protocol.connection_lost() when the creation of transport failed

STINNER Victor report at bugs.python.org
Thu Jan 29 00:48:53 CET 2015


STINNER Victor added the comment:

> The call to loop.add_reader() should maybe be scheduled after the call to connection_made()? To ensure that protocol methods (feed_data) are not called before connection_made() has been called.

Fixed by:
---
changeset:   94360:1b35bef31bf8
branch:      3.4
tag:         tip
user:        Victor Stinner <victor.stinner at gmail.com>
date:        Thu Jan 29 00:36:51 2015 +0100
files:       Lib/asyncio/selector_events.py Lib/test/test_asyncio/test_selector_events.py
description:
asyncio: Fix _SelectorSocketTransport constructor

Only start reading when connection_made() has been called:
protocol.data_received() must not be called before protocol.connection_made().
---

Other fix related to this issue:
---
changeset:   94358:1da90ebae442
branch:      3.4
parent:      94355:263344bb2107
user:        Victor Stinner <victor.stinner at gmail.com>
date:        Thu Jan 29 00:35:56 2015 +0100
files:       Lib/asyncio/sslproto.py Lib/test/test_asyncio/test_sslproto.py
description:
asyncio: Fix SSLProtocol.eof_received()

Wake-up the waiter if it is not done yet.
---

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23333>
_______________________________________


More information about the Python-bugs-list mailing list