[issue24577] Document behavior (logging and call to connection_lost) on socket TimeoutError
Changes by R. David Murray rdmur...@bitdance.com: -- assignee: - docs@python components: +Documentation, asyncio nosy: +docs@python, gvanrossum, haypo, yselivanov stage: - needs patch type: - behavior versions: +Python 3.4, Python 3.5, Python 3.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24577 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24577] Document behavior (logging and call to connection_lost) on socket TimeoutError
New submission from R. David Murray: I saw _fatal_error tracebacks in my application log, and thought I had hit an asyncio bug, but according to https://github.com/python/asyncio/issues/135 this is the correct behavior. That issue ends with a request to open a documentation issue on the python tracker, but I don't think that was done (I couldn't find one, anyway), so I'm opening this one. At this point in time I have no idea where this would go in the docs. Maybe in the docs for connection_lost? -- messages: 246370 nosy: r.david.murray priority: normal severity: normal status: open title: Document behavior (logging and call to connection_lost) on socket TimeoutError ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24577 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
