[issue21376] asyncio docs refer to wrong TimeoutError

STINNER Victor added the comment: Thanks for the report. In fact, asyncio.TimeoutError was not documented at all. It should now be fixed. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue21376] asyncio docs refer to wrong TimeoutError

Roundup Robot added the comment: New changeset 6d90e8df01f4 by Victor Stinner in branch '3.4': Issue #21376: document asyncio.TimeoutError http://hg.python.org/cpython/rev/6d90e8df01f4 New changeset 03bb1077b362 by Victor Stinner in branch 'default': (Merge 3.4) Issue #21376: document asyncio.Ti

[issue21376] asyncio docs refer to wrong TimeoutError

Guido van Rossum added the comment: I considered this, and decided against unifying the two TimeoutErrors. First the builtin TimeoutError is specifically a subclass of OSError representing the case where errno is ETIMEDOUT. But asyncio.TimeoutError means nothing of the sort. Second, the prec

[issue21376] asyncio docs refer to wrong TimeoutError

Antoine Pitrou added the comment: Gasp. Perhaps concurrent.futures.TimeoutError can inherit from the standard TimeoutError? The following patch doesn't seem to disrupt the test suite: diff --git a/Lib/concurrent/futures/_base.py b/Lib/concurrent/futures/_base.py --- a/Lib/concurrent/futures/_ba

[issue21376] asyncio docs refer to wrong TimeoutError

New submission from Philip Sequeira: Example: https://docs.python.org/3.4/library/asyncio-task.html TimeoutError is mentioned several times, and links to the OSError subclass. However, the actual TimeoutError raised by asyncio stuff is the one from concurrent.futures, which is not compatible. T