Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | bpo-35715: Liberate return value of _process_worker (GH-11514) | Dave Chevell | 2019-03-16 | 1 | -0/+1 |
| | | | | ProcessPoolExecutor workers will hold the return value of their last task in memory until the next task is received. Since the return value has already been propagated to the parent process's Future (or has been discarded by this point), the object can be safely released. | ||||
* | bpo-33097: Fix submit accepting callable after executor shutdown by ↵ | Mark Nemec | 2018-04-10 | 1 | -0/+7 |
| | | | | | | interpreter exit (GH-6144) Executors in concurrent.futures accepted tasks after executor was shutdown by interpreter exit. Tasks were left in PENDING state forever. This fix changes submit to instead raise a RuntimeError. | ||||
* | bpo-33056 FIX leaking fd in concurrent.futures.ProcessPoolExecutor (#6084) | Thomas Moreau | 2018-03-12 | 1 | -2/+9 |
| | |||||
* | bpo-31699 Deadlocks in `concurrent.futures.ProcessPoolExecutor` with ↵ | Thomas Moreau | 2018-01-05 | 1 | -49/+159 |
| | | | | | | pickling error (#3895) Fix deadlocks in :class:`concurrent.futures.ProcessPoolExecutor` when task arguments or results cause pickling or unpickling errors. This should make sure that calls to the :class:`ProcessPoolExecutor` API always eventually return. | ||||
* | bpo-21423: Add an initializer argument to {Process,Thread}PoolExecutor (#4241) | Antoine Pitrou | 2017-11-04 | 1 | -7/+29 |
| | | | | | | * bpo-21423: Add an initializer argument to {Process,Thread}PoolExecutor * Fix docstring | ||||
* | bpo-31540: Allow passing multiprocessing context to ProcessPoolExecutor (#3682) | Thomas Moreau | 2017-10-03 | 1 | -29/+37 |
| | |||||
* | bpo-31326: ProcessPoolExecutor waits for the call queue thread (#3265) | Victor Stinner | 2017-09-02 | 1 | -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 Grzywacz | 2017-09-01 | 1 | -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 Hettinger | 2016-08-30 | 1 | -1/+1 |
| | |||||
* | Issue #25523: Further a-to-an corrections new in 3.5 | Martin Panter | 2015-11-02 | 1 | -1/+1 |
| | |||||
* | Issue #21817: When an exception is raised in a task submitted to a ↵ | Antoine Pitrou | 2015-01-17 | 1 | -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 Pitrou | 2014-10-04 | 1 | -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 proper | Brian Quinlan | 2014-05-17 | 1 | -0/+3 |
| | |||||
* | Fix import of SimpleQueue. | Richard Oudkerk | 2013-10-16 | 1 | -1/+2 |
| | |||||
* | #18741: merge with 3.3. | Ezio Melotti | 2013-08-17 | 1 | -2/+2 |
|\ | |||||
| * | #18741: fix more typos. Patch by Févry Thibault. | Ezio Melotti | 2013-08-17 | 1 | -2/+2 |
| | | |||||
* | | Issue #17914: Use os.cpu_count() instead of multiprocessing.cpu_count() where | Charles-François Natali | 2013-06-28 | 1 | -1/+1 |
| | | | | | | | | applicable. | ||||
* | | Issue #16284: Prevent keeping unnecessary references to worker functions in ↵ | Andrew Svetlov | 2012-11-03 | 1 | -0/+4 |
| | | | | | | | | concurrent.futures ThreadPoolExecutor. | ||||
* | | Fix concurrent.futures docstring typo: "Request Q" -> "Result Q". | Mark Dickinson | 2012-10-20 | 1 | -1/+1 |
|/ | |||||
* | Issue #12328: Fix multiprocessing's use of overlapped I/O on Windows. | Antoine Pitrou | 2012-03-05 | 1 | -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 Lagerwall | 2012-01-08 | 1 | -3/+0 |
|\ | |||||
| * | Issue #12364: Fix a hang in concurrent.futures.ProcessPoolExecutor. | Ross Lagerwall | 2012-01-08 | 1 | -6/+1 |
| | | |||||
| * | Close the call queue in concurrent.futures.ProcessPoolExecutor when | Antoine Pitrou | 2011-07-16 | 1 | -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 Xicluna | 2011-11-11 | 1 | -2/+1 |
| | | |||||
* | | Silence spurious "broken pipe" tracebacks when shutting down a ↵ | Antoine Pitrou | 2011-07-16 | 1 | -4/+7 |
| | | | | | | | | ProcessPoolExecutor. | ||||
* | | Fix potential resource leaks in concurrent.futures.ProcessPoolExecutor | Antoine Pitrou | 2011-07-16 | 1 | -1/+4 |
| | | | | | | | | by joining all queues and processes when shutdown() is called. | ||||
* | | Followup to 51c1f2cedb96 (and issue #12456): | Antoine Pitrou | 2011-07-03 | 1 | -10/+10 |
| | | | | | | | | qsize() raises NotImplementedError on OS X, don't use it. | ||||
* | | Issue #12456: fix a possible hang on shutdown of a ↵ | Antoine Pitrou | 2011-07-02 | 1 | -9/+21 |
| | | | | | | | | concurrent.futures.ProcessPoolExecutor. | ||||
* | | Issue #9205: concurrent.futures.ProcessPoolExecutor now detects killed | Antoine Pitrou | 2011-06-08 | 1 | -31/+74 |
| | | | | | | | | | | children and raises BrokenProcessPool in such a situation. Previously it would reliably freeze/deadlock. | ||||
* | | Fix typo in name of private function | Antoine Pitrou | 2011-05-03 | 1 | -7/+7 |
|\ \ | |/ | |||||
| * | Fix typo in name of private function | Antoine Pitrou | 2011-05-03 | 1 | -7/+7 |
| | | |||||
* | | Issue #11815: Use a light-weight SimpleQueue for the result queue in ↵ | Antoine Pitrou | 2011-04-12 | 1 | -2/+3 |
|/ | | | | concurrent.futures.ProcessPoolExecutor. | ||||
* | Issue #11815: Remove dead code in concurrent.futures (since a blocking Queue | Antoine Pitrou | 2011-04-12 | 1 | -44/+25 |
| | | | | cannot raise queue.Empty). | ||||
* | Issue #11635: Don't use polling in worker threads and processes launched by | Antoine Pitrou | 2011-03-26 | 1 | -48/+64 |
| | | | | concurrent.futures. | ||||
* | Issue #10798: Reject supporting concurrent.futures if the system has | Martin v. Löwis | 2011-01-03 | 1 | -0/+26 |
| | | | | too few POSIX semaphores. | ||||
* | Fix "seperate". | Georg Brandl | 2010-12-09 | 1 | -1/+1 |
| | |||||
* | Initial implementation of PEP 3148 | Brian Quinlan | 2010-09-18 | 1 | -0/+337 |