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. The docs as they are seem to suggest that something like "except TimeoutError" would be appropriate, when in fact that would not produce the expected behavior; "except asyncio.TimeoutError" is what you'd want.

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/_base.py
+++ b/Lib/concurrent/futures/_base.py
@@ -49,7 +49,7 @@ class CancelledError(Error):
     """The Future was cancelled."""
     pass
 
-class TimeoutError(Error):
+class TimeoutError(Error, TimeoutError):
     """The operation exceeded the given deadline."""
     pass

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 precedent is concurrent.futures.TimeoutError. The asyncio one is used under the same conditions as that one.

I think we should just update the links in the docs to be correct.

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.TimeoutError
http://hg.python.org/cpython/rev/03bb1077b362

Thanks for the report. In fact, asyncio.TimeoutError was not documented at all. It should now be fixed.