Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 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-32576: use queue.SimpleQueue in critical places (#5216) | Antoine Pitrou | 2018-01-18 | 1 | -1/+1 |
| | | | | Where a queue may be invoked from a weakref callback, we need to use the reentrant SimpleQueue. | ||||
* | bpo-21423: Add an initializer argument to {Process,Thread}PoolExecutor (#4241) | Antoine Pitrou | 2017-11-04 | 1 | -3/+48 |
| | | | | | | * bpo-21423: Add an initializer argument to {Process,Thread}PoolExecutor * Fix docstring | ||||
* | bpo-31249: Fix ref cycle in ThreadPoolExecutor (#3178) | Victor Stinner | 2017-08-22 | 1 | -2/+4 |
| | | | | | | | | | | | | | * bpo-31249: Fix ref cycle in ThreadPoolExecutor concurrent.futures: WorkItem.run() used by ThreadPoolExecutor now breaks a reference cycle between an exception object and the WorkItem object. ThreadPoolExecutor.shutdown() now also clears its threads set. * shutdown() now only clears threads if wait is true. * Revert changes on shutdown() | ||||
* | bpo-29212: Fix the ugly repr() ThreadPoolExecutor thread name. (#2315) | Gregory P. Smith | 2017-06-22 | 1 | -1/+7 |
| | | | | | | | bpo-29212: Fix the ugly ThreadPoolExecutor thread name. Fixes the newly introduced ugly default thread name for concurrent.futures thread.ThreadPoolExecutor threads. They'll now resemble the old <=3.5 threading default Thread-x names by being named ThreadPoolExecutor-y_n. | ||||
* | Issue #27895: Spelling fixes (Contributed by Ville Skyttä). | Raymond Hettinger | 2016-08-30 | 1 | -1/+1 |
| | |||||
* | Issue #27664: Add to concurrent.futures.thread.ThreadPoolExecutor() | Gregory P. Smith | 2016-08-07 | 1 | -3/+8 |
| | | | | the ability to specify a thread name prefix. | ||||
* | Closes #21527: Add default number of workers to ThreadPoolExecutor. (Claudiu ↵ | Guido van Rossum | 2014-09-02 | 1 | -1/+6 |
| | | | | Popa.) | ||||
* | Issue #21362: concurrent.futures does not validate that max_workers is proper | Brian Quinlan | 2014-05-17 | 1 | -0/+3 |
| | |||||
* | Issue #16284: Prevent keeping unnecessary references to worker functions in ↵ | Andrew Svetlov | 2012-11-03 | 1 | -0/+2 |
| | | | | concurrent.futures ThreadPoolExecutor. | ||||
* | Remove unused or redundant imports in concurrent.futures and multiprocessing. | Florent Xicluna | 2011-11-11 | 1 | -1/+1 |
| | |||||
* | Issue #11815: Remove dead code in concurrent.futures (since a blocking Queue | Antoine Pitrou | 2011-04-12 | 1 | -8/+4 |
| | | | | cannot raise queue.Empty). | ||||
* | Issue #11635: Don't use polling in worker threads and processes launched by | Antoine Pitrou | 2011-03-26 | 1 | -31/+29 |
| | | | | concurrent.futures. | ||||
* | Initial implementation of PEP 3148 | Brian Quinlan | 2010-09-18 | 1 | -0/+136 |