[issue11635] concurrent.futures uses polling

[Antoine Pitrou]

Antoine Pitrou <pitrou at free.fr> added the comment:

Ok, here is a patch. Summary:
- leave a minimal amount of polling (every 600 seconds) to avoid blocking forever if there's a bug (shouldn't happen of course, but who knows? especially with multiprocessing)
- when wanting to wakeup a worker, put None in its receiving queue
- remove periodic cleanup of thread references by using a weak dict instead
- in tests, compute runtime and make the test fail if the runtime exceeds 60 seconds (to report aforementioned synchronization bugs)

Tested under Linux (extensively) and Windows 7 (briefly).

----------
keywords: +patch
Added file: http://bugs.python.org/file21351/cfpolling2.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue11635>
_______________________________________