summaryrefslogtreecommitdiffstats
path: root/Lib/concurrent/futures/process.py
Commit message (Collapse)AuthorAgeFilesLines
* bpo-31326: ProcessPoolExecutor waits for the call queue thread (#3265)Victor Stinner2017-09-011-1/+5
| | | | | | | | | | * bpo-31326: ProcessPoolExecutor waits for the call queue thread concurrent.futures.ProcessPoolExecutor.shutdown() now explicitly closes the call queue. Moreover, shutdown(wait=True) now also join the call queue thread, to prevent leaking a dangling thread. * Fix for shutdown() being called twice.
* bpo-27144: concurrent.futures as_complete and map iterators do not keep ↵Grzegorz Grzywacz2017-09-011-1/+13
| | | | | | | | | | reference to returned object (#1560) * bpo-27144: concurrent.futures as_complie and map iterators do not keep reference to returned object * Some nits. Improve wordings in docstrings and comments, and avoid relying on sys.getrefcount() in tests.
* Issue #27895: Spelling fixes (Contributed by Ville Skyttä).Raymond Hettinger2016-08-301-1/+1
|
* Issue #25523: Further a-to-an corrections new in 3.5Martin Panter2015-11-021-1/+1
|
* Issue #21817: When an exception is raised in a task submitted to a ↵Antoine Pitrou2015-01-171-2/+24
| | | | | | ProcessPoolExecutor, the remote traceback is now displayed in the parent process. Patch by Claudiu Popa.
* Issue #11271: concurrent.futures.Executor.map() now takes a *chunksize*Antoine Pitrou2014-10-041-0/+51
| | | | | argument to allow batching of tasks in child processes and improve performance of ProcessPoolExecutor. Patch by Dan O'Reilly.
* Issue #21362: concurrent.futures does not validate that max_workers is properBrian Quinlan2014-05-171-0/+3
|
* Fix import of SimpleQueue.Richard Oudkerk2013-10-161-1/+2
|
* #18741: merge with 3.3.Ezio Melotti2013-08-171-2/+2
|\
| * #18741: fix more typos. Patch by Févry Thibault.Ezio Melotti2013-08-171-2/+2
| |
* | Issue #17914: Use os.cpu_count() instead of multiprocessing.cpu_count() whereCharles-François Natali2013-06-281-1/+1
| | | | | | | | applicable.
* | Issue #16284: Prevent keeping unnecessary references to worker functions in ↵Andrew Svetlov2012-11-031-0/+4
| | | | | | | | concurrent.futures ThreadPoolExecutor.
* | Fix concurrent.futures docstring typo: "Request Q" -> "Result Q".Mark Dickinson2012-10-201-1/+1
|/
* Issue #12328: Fix multiprocessing's use of overlapped I/O on Windows.Antoine Pitrou2012-03-051-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also, add a multiprocessing.connection.wait(rlist, timeout=None) function for polling multiple objects at once. Patch by sbt. Complete changelist from sbt's patch: * Adds a wait(rlist, timeout=None) function for polling multiple objects at once. On Unix this is just a wrapper for select(rlist, [], [], timeout=None). * Removes use of the SentinelReady exception and the sentinels argument to certain methods. concurrent.futures.process has been changed to use wait() instead of SentinelReady. * Fixes bugs concerning PipeConnection.poll() and messages of zero length. * Fixes PipeListener.accept() to call ConnectNamedPipe() with overlapped=True. * Fixes Queue.empty() and SimpleQueue.empty() so that they are threadsafe on Windows. * Now PipeConnection.poll() and wait() will not modify the pipe except possibly by consuming a zero length message. (Previously poll() could consume a partial message.) * All of multiprocesing's pipe related blocking functions/methods are now interruptible by SIGINT on Windows.
* Merge with 3.2 for #12364.Ross Lagerwall2012-01-081-3/+0
|\
| * Issue #12364: Fix a hang in concurrent.futures.ProcessPoolExecutor.Ross Lagerwall2012-01-081-6/+1
| |
| * Close the call queue in concurrent.futures.ProcessPoolExecutor whenAntoine Pitrou2011-07-161-0/+1
| | | | | | | | shutdown() is called, without waiting for the garbage collector to kick in.
* | Remove unused or redundant imports in concurrent.futures and multiprocessing.Florent Xicluna2011-11-111-2/+1
| |
* | Silence spurious "broken pipe" tracebacks when shutting down a ↵Antoine Pitrou2011-07-151-4/+7
| | | | | | | | ProcessPoolExecutor.
* | Fix potential resource leaks in concurrent.futures.ProcessPoolExecutorAntoine Pitrou2011-07-151-1/+4
| | | | | | | | by joining all queues and processes when shutdown() is called.
* | Followup to 51c1f2cedb96 (and issue #12456):Antoine Pitrou2011-07-031-10/+10
| | | | | | | | qsize() raises NotImplementedError on OS X, don't use it.
* | Issue #12456: fix a possible hang on shutdown of a ↵Antoine Pitrou2011-07-021-9/+21
| | | | | | | | concurrent.futures.ProcessPoolExecutor.
* | Issue #9205: concurrent.futures.ProcessPoolExecutor now detects killedAntoine Pitrou2011-06-081-31/+74
| | | | | | | | | | children and raises BrokenProcessPool in such a situation. Previously it would reliably freeze/deadlock.
* | Fix typo in name of private functionAntoine Pitrou2011-05-031-7/+7
|\ \ | |/
| * Fix typo in name of private functionAntoine Pitrou2011-05-031-7/+7
| |
* | Issue #11815: Use a light-weight SimpleQueue for the result queue in ↵Antoine Pitrou2011-04-121-2/+3
|/ | | | concurrent.futures.ProcessPoolExecutor.
* Issue #11815: Remove dead code in concurrent.futures (since a blocking QueueAntoine Pitrou2011-04-121-44/+25
| | | | cannot raise queue.Empty).
* Issue #11635: Don't use polling in worker threads and processes launched byAntoine Pitrou2011-03-261-48/+64
| | | | concurrent.futures.
* Issue #10798: Reject supporting concurrent.futures if the system hasMartin v. Löwis2011-01-031-0/+26
| | | | too few POSIX semaphores.
* Fix "seperate".Georg Brandl2010-12-091-1/+1
|
* Initial implementation of PEP 3148Brian Quinlan2010-09-181-0/+337
generated by cgit v0.12 at 2025-04-27 03:33:30 (GMT)