Lines Matching refs:ProcessPoolExecutor

430   ``ProcessPoolExecutor`` shutdown could hang after a future has been
2528   :class:`concurrent.futures.ProcessPoolExecutor` are no longer spawned on
3031 - gh-issue-90622: In ``concurrent.futures.process.ProcessPoolExecutor``
3126 - bpo-46787: Fix :class:`concurrent.futures.ProcessPoolExecutor` exception
5501   :class:`concurrent.futures.ProcessPoolExecutor`. This allows users to
5511   :class:`ProcessPoolExecutor`.
9362 - bpo-40692: In the :class:`concurrent.futures.ProcessPoolExecutor`,
9366   :class:`ProcessPoolExecutor` on those platforms.
12793 - bpo-39207: Workers in :class:`~concurrent.futures.ProcessPoolExecutor` are
13306   :class:`concurrent.futures.ProcessPoolExecutor` to make it easier to
17004 - bpo-26903: Limit `max_workers` in `ProcessPoolExecutor` to 61 to work
18092 - bpo-35715: Librates the return value of a ProcessPoolExecutor
20296   concurrent.futures.ProcessPoolExecutor.
20489 - bpo-29877: compileall: import ProcessPoolExecutor only when needed,
22050   concurrent.futures.ProcessPoolExecutor.
22560   ``ProcessPoolExecutor`` lazily (using :pep:`562`). It makes ``import
22995   :class:`concurrent.futures.ProcessPoolExecutor` when task arguments or
22997   calls to the :class:`ProcessPoolExecutor` API always eventually return.
23800   :class:`concurrent.futures.ProcessPoolExecutor` constructor. Also, free
23801   job resources in :class:`concurrent.futures.ProcessPoolExecutor` earlier
24476 - bpo-31326: concurrent.futures.ProcessPoolExecutor.shutdown() now
34477 - bpo-23917: Fall back to sequential compilation when ProcessPoolExecutor
35432   ProcessPoolExecutor, the remote traceback is now displayed in the parent
35720   performance of ProcessPoolExecutor.  Patch by Dan O'Reilly.