1. b713adf bpo-31326: ProcessPoolExecutor waits for the call queue thread (#3265) by Victor Stinner · 7 years ago
  2. 97e1b1c bpo-27144: concurrent.futures as_complete and map iterators do not keep reference to returned object (#1560) by Grzegorz Grzywacz · 7 years ago
  3. 15f44ab Issue #27895: Spelling fixes (Contributed by Ville Skyttä). by Raymond Hettinger · 8 years ago
  4. d2ad571 Issue #25523: Further a-to-an corrections new in 3.5 by Martin Panter · 9 years ago
  5. 1285c9b Issue #21817: When an exception is raised in a task submitted to a ProcessPoolExecutor, the remote traceback is now displayed in the parent process. by Antoine Pitrou · 10 years ago
  6. 4aae276 Issue #11271: concurrent.futures.Executor.map() now takes a *chunksize* by Antoine Pitrou · 10 years ago
  7. 20efceb Issue #21362: concurrent.futures does not validate that max_workers is proper by Brian Quinlan · 10 years ago
  8. 1f2eaa9 Fix import of SimpleQueue. by Richard Oudkerk · 11 years ago
  9. e0c6916 #18741: merge with 3.3. by Ezio Melotti · 11 years ago
  10. b5bc353 #18741: fix more typos. Patch by Févry Thibault. by Ezio Melotti · 11 years ago
  11. 37cfb0a Issue #17914: Use os.cpu_count() instead of multiprocessing.cpu_count() where by Charles-François Natali · 11 years ago
  12. 6b97374 Issue #16284: Prevent keeping unnecessary references to worker functions in concurrent.futures ThreadPoolExecutor. by Andrew Svetlov · 12 years ago
  13. 5ee2404 Fix concurrent.futures docstring typo: "Request Q" -> "Result Q". by Mark Dickinson · 12 years ago
  14. bdb1cf1 Issue #12328: Fix multiprocessing's use of overlapped I/O on Windows. by Antoine Pitrou · 13 years ago
  15. 69f39a5 Merge with 3.2 for #12364. by Ross Lagerwall · 13 years ago
  16. 66e2fb6 Issue #12364: Fix a hang in concurrent.futures.ProcessPoolExecutor. by Ross Lagerwall · 13 years ago
  17. 04842a8 Remove unused or redundant imports in concurrent.futures and multiprocessing. by Florent Xicluna · 13 years ago
  18. 0b44795 Close the call queue in concurrent.futures.ProcessPoolExecutor when by Antoine Pitrou · 13 years ago
  19. dc19c24 Silence spurious "broken pipe" tracebacks when shutting down a ProcessPoolExecutor. by Antoine Pitrou · 13 years ago
  20. d06a065 Fix potential resource leaks in concurrent.futures.ProcessPoolExecutor by Antoine Pitrou · 13 years ago
  21. 1c405b3 Followup to 51c1f2cedb96 (and issue #12456): by Antoine Pitrou · 13 years ago
  22. 020436b Issue #12456: fix a possible hang on shutdown of a concurrent.futures.ProcessPoolExecutor. by Antoine Pitrou · 13 years ago
  23. dd69649 Issue #9205: concurrent.futures.ProcessPoolExecutor now detects killed by Antoine Pitrou · 13 years ago
  24. 441f935 Fix typo in name of private function by Antoine Pitrou · 13 years ago
  25. b87a56a Fix typo in name of private function by Antoine Pitrou · 13 years ago
  26. b7877f2 Issue #11815: Use a light-weight SimpleQueue for the result queue in concurrent.futures.ProcessPoolExecutor. by Antoine Pitrou · 14 years ago
  27. 27be5da Issue #11815: Remove dead code in concurrent.futures (since a blocking Queue by Antoine Pitrou · 14 years ago
  28. c13d454 Issue #11635: Don't use polling in worker threads and processes launched by by Antoine Pitrou · 14 years ago
  29. 9f6d48b Issue #10798: Reject supporting concurrent.futures if the system has by Martin v. Löwis · 14 years ago
  30. fb1720b Fix "seperate". by Georg Brandl · 14 years ago
  31. 81c4d36 Initial implementation of PEP 3148 by Brian Quinlan · 14 years ago