This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Document asyncio behavior (logging and call to connection_lost) on socket TimeoutError
Type: behavior Stage: needs patch
Components: asyncio, Documentation Versions: Python 3.6, Python 3.4, Python 3.5
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, gvanrossum, r.david.murray, vstinner, yselivanov
Priority: normal Keywords:

Created on 2015-07-06 15:14 by r.david.murray, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg246370 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2015-07-06 15:14
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?
History
Date User Action Args
2022-04-11 14:58:18adminsetgithub: 68765
2015-07-06 15:36:36r.david.murraysettitle: Document behavior (logging and call to connection_lost) on socket TimeoutError -> Document asyncio behavior (logging and call to connection_lost) on socket TimeoutError
2015-07-06 15:16:02r.david.murraysetnosy: + yselivanov, docs@python, vstinner, gvanrossum
versions: + Python 3.4, Python 3.5, Python 3.6
assignee: docs@python
components: + Documentation, asyncio
type: behavior
stage: needs patch
2015-07-06 15:14:36r.david.murraycreate