[issue35840] Control flow inconsistency on closed asyncio stream

Emmanuel Arias added the comment: Ok, I am working on that. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35840] Control flow inconsistency on closed asyncio stream

Marc Schlaich added the comment: No, I'm seeing the same issue on MacOS. Attached modified example. -- Added file: https://bugs.python.org/file48160/tcp_test.py ___ Python tracker

[issue35840] Control flow inconsistency on closed asyncio stream

Emmanuel Arias added the comment: I think that this issue is just for Windows right? I add Windows to required a Windows' dev. -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker

[issue35840] Control flow inconsistency on closed asyncio stream

Change by Emmanuel Arias : -- nosy: +eamanu ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35840] Control flow inconsistency on closed asyncio stream

Marc Schlaich added the comment: After having a closer look I fear that there isn't a correct implementation for half closed sockets and returning True from eof_received results in a fundamentally broken state machine. I'm not sure if a selector implementation can handle half closed

[issue35840] Control flow inconsistency on closed asyncio stream

New submission from Marc Schlaich : After closing a StreamWriter the `StreamReaderProtocol.connection_lost` on the other end is not getting called. In this case the StreamReader is at EOF but calling write/drain does not raise any Exception (and sending data to Nirvana). I would expect that