Ryder Lewis added the comment:
I attached a small patch that fixes the documentation, and also documents the
other missing exceptions from concurrent.futures documentation.
--
keywords: +patch
Added file: http://bugs.python.org/file39029/issue23962.patch
New submission from Ryder Lewis:
The documentation at https://docs.python.org/3/library/concurrent.futures.html
has several functions that case raise a TimeoutError. The hyperlink generated
for TimeoutError links to the built-in exception
https://docs.python.org/3/library/exceptions.html
Changes by Ryder Lewis :
--
nosy: +ryder.lewis
___
Python tracker
<http://bugs.python.org/issue21886>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Ryder Lewis:
I'm not sure if this is a bug or expected behavior, but basically what I want
to do is log the timestamp when an application exits. Sample script to
illustrate the issue:
try.py
import time
class A():
def __init__(self):
Ryder Lewis added the comment:
Another run raised a different exception,
again running ./example.py http://www.yahoo.com/
Timed out with 0.05-second timeout
HTTP header> HTTP/1.0 301 Redirect
HTTP header> Date: Tue, 06 May 2014 18:58:53 GMT
HTTP header> Connection: close
HTTP header&g
New submission from Ryder Lewis:
Intermittently, when using asyncio.wait_for() with asyncio.open_connection() to
cancel the open_connection() task after a timeout period, an
asyncio.futures.InvalidStateError is raised. It seems to be a race condition,
if the open_connection() call succeeds
