[issue26278] BaseTransport.close() does not trigger connection_lost()

Sümer Cip added the comment: Closing the issue seems like a good idea: as it seems nobody seems to have spotted similar issue and I have only been able to reproduce it in Python 3.4. Just for future ref.: The uncommon thing is that the server I was using is a TCP game server holding long

[issue38522] Py_USING_MEMORY_DEBUGGER is referenced in docs but not present in code

Change by Sümer Cip : -- versions: +Python 2.7, Python 3.5 ___ Python tracker <https://bugs.python.org/issue38522> ___ ___ Python-bugs-list mailing list Unsub

[issue38522] Py_USING_MEMORY_DEBUGGER is referenced in docs but not present in code

New submission from Sümer Cip : Hi all, While trying to debug Python C extension via valgrind, I was reading the document Misc/README.valgrind and it seems there are some parts not being uptodate. There is comments comments like following: Uncomment Py_USING_MEMORY_DEBUGGER in Objects

[issue26278] BaseTransport.close() does not trigger connection_lost()

Sümer Cip added the comment: I do not know I still have the issue since I have circumvented the problem. I have been using Python3.4, I think it was one of the earliest asyncio implementations. The way it can be reproduced is as following: 1) There are lots of active TCP connections

[issue26278] BaseTransport.close() does not trigger connection_lost()

New submission from Sümer Cip: Hi all, We have implemented a TCP server based on asyncio. And while doing some regression tests we randomly see following error: 1) Client connects to the server. 2) Client is closed ungracefully(without sending a FIN, deplug cable) 3) We have a custom PING