Josh Rosenberg added the comment:
The docs (
https://docs.python.org/3/library/concurrent.futures.html#concurrent.futures.as_completed
) do seem to indicate it shouldn't do so as long as results were available
before the timeout expired:
"The returned iterator raises a concurrent.futures.Time
New submission from jiangwanwei:
when I use as_completed function to wait my futures, if I sleep more than
timeout seconds in each iteration , I found that futures has been set result,
but raise TimeoutError. as my test example code shows:
from concurrent import futures
from multiprocessing im
