Mr.Combet Webshell 🔥

Edit File Name : concurrent.futures.html

<!DOCTYPE html>

<title>concurrent.futures — Launching parallel tasks &#8212; Python 3.12.3 documentation</title><meta name="viewport" content="width=device-width, initial-scale=1.0">
 
 <link rel="stylesheet" type="text/css" href="../_static/pygments.css?v=80d5e7a1" />
 <link rel="stylesheet" type="text/css" href="../_static/pydoctheme.css?v=bb723527" />
 <link id="pygments_dark_css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css" href="../_static/pygments_dark.css?v=b20cc3f5" />
 
 <script src="../_static/documentation_options.js?v=2c828074"></script>
 <script src="../_static/doctools.js?v=888ff710"></script>
 <script src="../_static/sphinx_highlight.js?v=dc90522c"></script>
 
 <script src="../_static/sidebar.js"></script>
 
 <link rel="search" type="application/opensearchdescription+xml"
 title="Search within Python 3.12.3 documentation"
 href="../_static/opensearch.xml"/>
 <link rel="author" title="About these documents" href="../about.html" />
 <link rel="index" title="Index" href="../genindex.html" />
 <link rel="search" title="Search" href="../search.html" />
 <link rel="copyright" title="Copyright" href="../copyright.html" />
 <link rel="next" title="subprocess — Subprocess management" href="subprocess.html" />
 <link rel="prev" title="The concurrent package" href="concurrent.html" />
 <link rel="canonical" href="https://docs.python.org/3/library/concurrent.futures.html" />

</head>
<body>
<div class="mobile-nav">
 <input type="checkbox" id="menuToggler" class="toggler__input" aria-controls="navigation"
 aria-pressed="false" aria-expanded="false" role="button" aria-label="Menu" />
 <nav class="nav-content" role="navigation">
 <label for="menuToggler" class="toggler__label">
 
 </label>
 
 <a href="https://www.python.org/" class="nav-logo">
 <img src="../_static/py.svg" alt="Python logo"/>
 </a>
 
 <form role="search" class="search" action="../search.html" method="get">
 <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" class="search-icon">
 <path fill-rule="nonzero" fill="currentColor" d="M15.5 14h-.79l-.28-.27a6.5 6.5 0 001.48-5.34c-.47-2.78-2.79-5-5.59-5.34a6.505 6.505 0 00-7.27 7.27c.34 2.8 2.56 5.12 5.34 5.59a6.5 6.5 0 005.34-1.48l.27.28v.79l4.25 4.25c.41.41 1.08.41 1.49 0 .41-.41.41-1.08 0-1.49L15.5 14zm-6 0C7.01 14 5 11.99 5 9.5S7.01 5 9.5 5 14 7.01 14 9.5 11.99 14 9.5 14z"></path>
 </svg>
 <input placeholder="Quick search" aria-label="Quick search" type="search" name="q" />
 <input type="submit" value="Go"/>
 </form>
 
 </nav>
 <div class="menu-wrapper">
 <nav class="menu" role="navigation" aria-label="main navigation">
 <div class="language_switcher_placeholder"></div>
 
<label class="theme-selector-label">
 Theme
 <select class="theme-selector" oninput="activateTheme(this.value)">
 <option value="auto" selected>Auto</option>
 <option value="light">Light</option>
 <option value="dark">Dark</option>
 </select>
</label>
 <div>
 <h3><a href="../contents.html">Table of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#"><code class="xref py py-mod docutils literal notranslate">concurrent.futures</code> — Launching parallel tasks</a><ul>
<li><a class="reference internal" href="#executor-objects">Executor Objects</a></li>
<li><a class="reference internal" href="#threadpoolexecutor">ThreadPoolExecutor</a><ul>
<li><a class="reference internal" href="#threadpoolexecutor-example">ThreadPoolExecutor Example</a></li>
</ul>
</li>
<li><a class="reference internal" href="#processpoolexecutor">ProcessPoolExecutor</a><ul>
<li><a class="reference internal" href="#processpoolexecutor-example">ProcessPoolExecutor Example</a></li>
</ul>
</li>
<li><a class="reference internal" href="#future-objects">Future Objects</a></li>
<li><a class="reference internal" href="#module-functions">Module Functions</a></li>
<li><a class="reference internal" href="#exception-classes">Exception classes</a></li>
</ul>
</li>
</ul>

</div>
 <div>
 <h4>Previous topic</h4>
 <a href="concurrent.html"
 title="previous chapter">The <code class="xref py py-mod docutils literal notranslate">concurrent</code> package</a>
 </div>
 <div>
 <h4>Next topic</h4>
 <a href="subprocess.html"
 title="next chapter"><code class="xref py py-mod docutils literal notranslate">subprocess</code> — Subprocess management</a>
 </div>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../bugs.html">Report a Bug</a></li>
 <li>
 <a href="https://github.com/python/cpython/blob/main/Doc/library/concurrent.futures.rst"
 rel="nofollow">Show Source
 </a>
 </li>
 </ul>
 </div>
 </nav>
 </div>
</div>

<div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 accesskey="I">index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="subprocess.html" title="subprocess — Subprocess management"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="concurrent.html" title="The concurrent package"
 accesskey="P">previous</a> |</li>

<li><img src="../_static/py.svg" alt="Python logo" style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="https://www.python.org/">Python</a> &#187;</li>
 <li class="switchers">
 <div class="language_switcher_placeholder"></div>
 <div class="version_switcher_placeholder"></div>
 </li>
 <li>
 
 </li>
 <li id="cpython-language-and-version">
 <a href="../index.html">3.12.3 Documentation</a> &#187;
 </li>

<li class="nav-item nav-item-1"><a href="index.html" >The Python Standard Library</a> &#187;</li>
 <li class="nav-item nav-item-2"><a href="concurrency.html" accesskey="U">Concurrent Execution</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href=""><code class="xref py py-mod docutils literal notranslate">concurrent.futures</code> — Launching parallel tasks</a></li>
 <li class="right">

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body" role="main">
 
 <section id="module-concurrent.futures">
<h1><a class="reference internal" href="#module-concurrent.futures" title="concurrent.futures: Execute computations concurrently using threads or processes."><code class="xref py py-mod docutils literal notranslate">concurrent.futures</code></a> — Launching parallel tasks<a class="headerlink" href="#module-concurrent.futures" title="Link to this heading">¶</a></h1>
<div class="versionadded">
New in version 3.2.
</div>
Source code: <a class="reference external" href="https://github.com/python/cpython/tree/3.12/Lib/concurrent/futures/thread.py">Lib/concurrent/futures/thread.py</a>
and <a class="reference external" href="https://github.com/python/cpython/tree/3.12/Lib/concurrent/futures/process.py">Lib/concurrent/futures/process.py</a>
<hr class="docutils" />
The <a class="reference internal" href="#module-concurrent.futures" title="concurrent.futures: Execute computations concurrently using threads or processes."><code class="xref py py-mod docutils literal notranslate">concurrent.futures</code></a> module provides a high-level interface for
asynchronously executing callables.
The asynchronous execution can be performed with threads, using
<a class="reference internal" href="#concurrent.futures.ThreadPoolExecutor" title="concurrent.futures.ThreadPoolExecutor"><code class="xref py py-class docutils literal notranslate">ThreadPoolExecutor</code></a>, or separate processes, using
<a class="reference internal" href="#concurrent.futures.ProcessPoolExecutor" title="concurrent.futures.ProcessPoolExecutor"><code class="xref py py-class docutils literal notranslate">ProcessPoolExecutor</code></a>. Both implement the same interface, which is
defined by the abstract <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> class.
<div class="availability docutils container">
<a class="reference internal" href="intro.html#availability">Availability</a>: not Emscripten, not WASI.
This module does not work or is not available on WebAssembly platforms
<code class="docutils literal notranslate">wasm32-emscripten</code> and <code class="docutils literal notranslate">wasm32-wasi</code>. See
<a class="reference internal" href="intro.html#wasm-availability">WebAssembly platforms</a> for more information.
</div>
<section id="executor-objects">
<h2>Executor Objects<a class="headerlink" href="#executor-objects" title="Link to this heading">¶</a></h2>
<dl class="py class">
<dt class="sig sig-object py" id="concurrent.futures.Executor">
class concurrent.futures.Executor<a class="headerlink" href="#concurrent.futures.Executor" title="Link to this definition">¶</a></dt>
<dd>An abstract class that provides methods to execute calls asynchronously. It
should not be used directly, but through its concrete subclasses.
<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Executor.submit">
submit(fn, /, *args, **kwargs)<a class="headerlink" href="#concurrent.futures.Executor.submit" title="Link to this definition">¶</a></dt>
<dd>Schedules the callable, fn, to be executed as <code class="docutils literal notranslate">fn(*args, **kwargs)</code>
and returns a <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> object representing the execution of the
callable.
<div class="highlight-python3 notranslate"><div class="highlight"><pre>with ThreadPoolExecutor(max_workers=1) as executor:
 future = executor.submit(pow, 323, 1235)
 print(future.result())
</pre></div>
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Executor.map">
map(fn, *iterables, timeout=None, chunksize=1)<a class="headerlink" href="#concurrent.futures.Executor.map" title="Link to this definition">¶</a></dt>
<dd>Similar to <a class="reference internal" href="functions.html#map" title="map"><code class="xref py py-func docutils literal notranslate">map(fn, *iterables)</code></a> except:
<ul class="simple">
<li>the iterables are collected immediately rather than lazily;</li>
<li>fn is executed asynchronously and several calls to
fn may be made concurrently.</li>
</ul>
The returned iterator raises a <a class="reference internal" href="exceptions.html#TimeoutError" title="TimeoutError"><code class="xref py py-exc docutils literal notranslate">TimeoutError</code></a>
if <a class="reference internal" href="stdtypes.html#iterator.__next__" title="iterator.__next__"><code class="xref py py-meth docutils literal notranslate">__next__()</code></a> is called and the result isn’t available
after timeout seconds from the original call to <a class="reference internal" href="#concurrent.futures.Executor.map" title="concurrent.futures.Executor.map"><code class="xref py py-meth docutils literal notranslate">Executor.map()</code></a>.
timeout can be an int or a float. If timeout is not specified or
<code class="docutils literal notranslate">None</code>, there is no limit to the wait time.
If a fn call raises an exception, then that exception will be
raised when its value is retrieved from the iterator.
When using <a class="reference internal" href="#concurrent.futures.ProcessPoolExecutor" title="concurrent.futures.ProcessPoolExecutor"><code class="xref py py-class docutils literal notranslate">ProcessPoolExecutor</code></a>, this method chops iterables
into a number of chunks which it submits to the pool as separate
tasks. The (approximate) size of these chunks can be specified by
setting chunksize to a positive integer. For very long iterables,
using a large value for chunksize can significantly improve
performance compared to the default size of 1. With
<a class="reference internal" href="#concurrent.futures.ThreadPoolExecutor" title="concurrent.futures.ThreadPoolExecutor"><code class="xref py py-class docutils literal notranslate">ThreadPoolExecutor</code></a>, chunksize has no effect.
<div class="versionchanged">
Changed in version 3.5: Added the chunksize argument.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Executor.shutdown">
shutdown(wait=True, *, cancel_futures=False)<a class="headerlink" href="#concurrent.futures.Executor.shutdown" title="Link to this definition">¶</a></dt>
<dd>Signal the executor that it should free any resources that it is using
when the currently pending futures are done executing. Calls to
<a class="reference internal" href="#concurrent.futures.Executor.submit" title="concurrent.futures.Executor.submit"><code class="xref py py-meth docutils literal notranslate">Executor.submit()</code></a> and <a class="reference internal" href="#concurrent.futures.Executor.map" title="concurrent.futures.Executor.map"><code class="xref py py-meth docutils literal notranslate">Executor.map()</code></a> made after shutdown will
raise <a class="reference internal" href="exceptions.html#RuntimeError" title="RuntimeError"><code class="xref py py-exc docutils literal notranslate">RuntimeError</code></a>.
If wait is <code class="docutils literal notranslate">True</code> then this method will not return until all the
pending futures are done executing and the resources associated with the
executor have been freed. If wait is <code class="docutils literal notranslate">False</code> then this method will
return immediately and the resources associated with the executor will be
freed when all pending futures are done executing. Regardless of the
value of wait, the entire Python program will not exit until all
pending futures are done executing.
If cancel_futures is <code class="docutils literal notranslate">True</code>, this method will cancel all pending
futures that the executor has not started running. Any futures that
are completed or running won’t be cancelled, regardless of the value
of cancel_futures.
If both cancel_futures and wait are <code class="docutils literal notranslate">True</code>, all futures that the
executor has started running will be completed prior to this method
returning. The remaining futures are cancelled.
You can avoid having to call this method explicitly if you use the
<a class="reference internal" href="../reference/compound_stmts.html#with"><code class="xref std std-keyword docutils literal notranslate">with</code></a> statement, which will shutdown the <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a>
(waiting as if <a class="reference internal" href="#concurrent.futures.Executor.shutdown" title="concurrent.futures.Executor.shutdown"><code class="xref py py-meth docutils literal notranslate">Executor.shutdown()</code></a> were called with wait set to
<code class="docutils literal notranslate">True</code>):
<div class="highlight-python3 notranslate"><div class="highlight"><pre>import shutil
with ThreadPoolExecutor(max_workers=4) as e:
 e.submit(shutil.copy, &#39;src1.txt&#39;, &#39;dest1.txt&#39;)
 e.submit(shutil.copy, &#39;src2.txt&#39;, &#39;dest2.txt&#39;)
 e.submit(shutil.copy, &#39;src3.txt&#39;, &#39;dest3.txt&#39;)
 e.submit(shutil.copy, &#39;src4.txt&#39;, &#39;dest4.txt&#39;)
</pre></div>
</div>
<div class="versionchanged">
Changed in version 3.9: Added cancel_futures.
</div>
</dd></dl>

</dd></dl>

</section>
<section id="threadpoolexecutor">
<h2>ThreadPoolExecutor<a class="headerlink" href="#threadpoolexecutor" title="Link to this heading">¶</a></h2>
<a class="reference internal" href="#concurrent.futures.ThreadPoolExecutor" title="concurrent.futures.ThreadPoolExecutor"><code class="xref py py-class docutils literal notranslate">ThreadPoolExecutor</code></a> is an <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> subclass that uses a pool of
threads to execute calls asynchronously.
Deadlocks can occur when the callable associated with a <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> waits on
the results of another <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a>. For example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>import time
def wait_on_b():
 time.sleep(5)
 print(b.result()) # b will never complete because it is waiting on a.
 return 5

def wait_on_a():
 time.sleep(5)
 print(a.result()) # a will never complete because it is waiting on b.
 return 6

executor = ThreadPoolExecutor(max_workers=1)
executor.submit(wait_on_future)
</pre></div>
</div>
<dl class="py class">
<dt class="sig sig-object py" id="concurrent.futures.ThreadPoolExecutor">
class concurrent.futures.ThreadPoolExecutor(max_workers=None, thread_name_prefix='', initializer=None, initargs=())<a class="headerlink" href="#concurrent.futures.ThreadPoolExecutor" title="Link to this definition">¶</a></dt>
<dd>An <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> subclass that uses a pool of at most max_workers
threads to execute calls asynchronously.
All threads enqueued to <code class="docutils literal notranslate">ThreadPoolExecutor</code> will be joined before the
interpreter can exit. Note that the exit handler which does this is
executed before any exit handlers added using <code class="docutils literal notranslate">atexit</code>. This means
exceptions in the main thread must be caught and handled in order to
signal threads to exit gracefully. For this reason, it is recommended
that <code class="docutils literal notranslate">ThreadPoolExecutor</code> not be used for long-running tasks.
initializer is an optional callable that is called at the start of
each worker thread; initargs is a tuple of arguments passed to the
initializer. Should initializer raise an exception, all currently
pending jobs will raise a <a class="reference internal" href="#concurrent.futures.thread.BrokenThreadPool" title="concurrent.futures.thread.BrokenThreadPool"><code class="xref py py-exc docutils literal notranslate">BrokenThreadPool</code></a>,
as well as any attempt to submit more jobs to the pool.
<div class="versionchanged">
Changed in version 3.5: If max_workers is <code class="docutils literal notranslate">None</code> or
not given, it will default to the number of processors on the machine,
multiplied by <code class="docutils literal notranslate">5</code>, assuming that <a class="reference internal" href="#concurrent.futures.ThreadPoolExecutor" title="concurrent.futures.ThreadPoolExecutor"><code class="xref py py-class docutils literal notranslate">ThreadPoolExecutor</code></a> is often
used to overlap I/O instead of CPU work and the number of workers
should be higher than the number of workers
for <a class="reference internal" href="#concurrent.futures.ProcessPoolExecutor" title="concurrent.futures.ProcessPoolExecutor"><code class="xref py py-class docutils literal notranslate">ProcessPoolExecutor</code></a>.
</div>
<div class="versionchanged">
Changed in version 3.6: Added the thread_name_prefix parameter to allow users to
control the <a class="reference internal" href="threading.html#threading.Thread" title="threading.Thread"><code class="xref py py-class docutils literal notranslate">threading.Thread</code></a> names for worker threads created by
the pool for easier debugging.
</div>
<div class="versionchanged">
Changed in version 3.7: Added the initializer and initargs arguments.
</div>
<div class="versionchanged">
Changed in version 3.8: Default value of max_workers is changed to <code class="docutils literal notranslate">min(32, os.cpu_count() + 4)</code>.
This default value preserves at least 5 workers for I/O bound tasks.
It utilizes at most 32 CPU cores for CPU bound tasks which release the GIL.
And it avoids using very large resources implicitly on many-core machines.
ThreadPoolExecutor now reuses idle worker threads before starting
max_workers worker threads too.
</div>
</dd></dl>

<section id="threadpoolexecutor-example">
<h3>ThreadPoolExecutor Example<a class="headerlink" href="#threadpoolexecutor-example" title="Link to this heading">¶</a></h3>
<div class="highlight-python3 notranslate"><div class="highlight"><pre>import concurrent.futures
import urllib.request

URLS = [&#39;http://www.foxnews.com/&#39;,
 &#39;http://www.cnn.com/&#39;,
 &#39;http://europe.wsj.com/&#39;,
 &#39;http://www.bbc.co.uk/&#39;,
 &#39;http://nonexistant-subdomain.python.org/&#39;]

# Retrieve a single page and report the URL and contents
def load_url(url, timeout):
 with urllib.request.urlopen(url, timeout=timeout) as conn:
 return conn.read()

# We can use a with statement to ensure threads are cleaned up promptly
with concurrent.futures.ThreadPoolExecutor(max_workers=5) as executor:
 # Start the load operations and mark each future with its URL
 future_to_url = {executor.submit(load_url, url, 60): url for url in URLS}
 for future in concurrent.futures.as_completed(future_to_url):
 url = future_to_url[future]
 try:
 data = future.result()
 except Exception as exc:
 print(&#39;%r generated an exception: %s&#39; % (url, exc))
 else:
 print(&#39;%r page is %d bytes&#39; % (url, len(data)))
</pre></div>
</div>
</section>
</section>
<section id="processpoolexecutor">
<h2>ProcessPoolExecutor<a class="headerlink" href="#processpoolexecutor" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#concurrent.futures.ProcessPoolExecutor" title="concurrent.futures.ProcessPoolExecutor"><code class="xref py py-class docutils literal notranslate">ProcessPoolExecutor</code></a> class is an <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> subclass that
uses a pool of processes to execute calls asynchronously.
<a class="reference internal" href="#concurrent.futures.ProcessPoolExecutor" title="concurrent.futures.ProcessPoolExecutor"><code class="xref py py-class docutils literal notranslate">ProcessPoolExecutor</code></a> uses the <a class="reference internal" href="multiprocessing.html#module-multiprocessing" title="multiprocessing: Process-based parallelism."><code class="xref py py-mod docutils literal notranslate">multiprocessing</code></a> module, which
allows it to side-step the <a class="reference internal" href="../glossary.html#term-global-interpreter-lock">Global Interpreter Lock</a> but also means that
only picklable objects can be executed and returned.
The <code class="docutils literal notranslate">__main__</code> module must be importable by worker subprocesses. This means
that <a class="reference internal" href="#concurrent.futures.ProcessPoolExecutor" title="concurrent.futures.ProcessPoolExecutor"><code class="xref py py-class docutils literal notranslate">ProcessPoolExecutor</code></a> will not work in the interactive interpreter.
Calling <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> or <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> methods from a callable submitted
to a <a class="reference internal" href="#concurrent.futures.ProcessPoolExecutor" title="concurrent.futures.ProcessPoolExecutor"><code class="xref py py-class docutils literal notranslate">ProcessPoolExecutor</code></a> will result in deadlock.
<dl class="py class">
<dt class="sig sig-object py" id="concurrent.futures.ProcessPoolExecutor">
class concurrent.futures.ProcessPoolExecutor(max_workers=None, mp_context=None, initializer=None, initargs=(), max_tasks_per_child=None)<a class="headerlink" href="#concurrent.futures.ProcessPoolExecutor" title="Link to this definition">¶</a></dt>
<dd>An <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> subclass that executes calls asynchronously using a pool
of at most max_workers processes. If max_workers is <code class="docutils literal notranslate">None</code> or not
given, it will default to the number of processors on the machine.
If max_workers is less than or equal to <code class="docutils literal notranslate">0</code>, then a <a class="reference internal" href="exceptions.html#ValueError" title="ValueError"><code class="xref py py-exc docutils literal notranslate">ValueError</code></a>
will be raised.
On Windows, max_workers must be less than or equal to <code class="docutils literal notranslate">61</code>. If it is not
then <a class="reference internal" href="exceptions.html#ValueError" title="ValueError"><code class="xref py py-exc docutils literal notranslate">ValueError</code></a> will be raised. If max_workers is <code class="docutils literal notranslate">None</code>, then
the default chosen will be at most <code class="docutils literal notranslate">61</code>, even if more processors are
available.
mp_context can be a <a class="reference internal" href="multiprocessing.html#module-multiprocessing" title="multiprocessing: Process-based parallelism."><code class="xref py py-mod docutils literal notranslate">multiprocessing</code></a> context or <code class="docutils literal notranslate">None</code>. It will be
used to launch the workers. If mp_context is <code class="docutils literal notranslate">None</code> or not given, the
default <a class="reference internal" href="multiprocessing.html#module-multiprocessing" title="multiprocessing: Process-based parallelism."><code class="xref py py-mod docutils literal notranslate">multiprocessing</code></a> context is used.
See <a class="reference internal" href="multiprocessing.html#multiprocessing-start-methods">Contexts and start methods</a>.
initializer is an optional callable that is called at the start of
each worker process; initargs is a tuple of arguments passed to the
initializer. Should initializer raise an exception, all currently
pending jobs will raise a <a class="reference internal" href="#concurrent.futures.process.BrokenProcessPool" title="concurrent.futures.process.BrokenProcessPool"><code class="xref py py-exc docutils literal notranslate">BrokenProcessPool</code></a>,
as well as any attempt to submit more jobs to the pool.
max_tasks_per_child is an optional argument that specifies the maximum
number of tasks a single process can execute before it will exit and be
replaced with a fresh worker process. By default max_tasks_per_child is
<code class="docutils literal notranslate">None</code> which means worker processes will live as long as the pool. When
a max is specified, the “spawn” multiprocessing start method will be used by
default in absence of a mp_context parameter. This feature is incompatible
with the “fork” start method.
<div class="versionchanged">
Changed in version 3.3: When one of the worker processes terminates abruptly, a
<a class="reference internal" href="#concurrent.futures.process.BrokenProcessPool" title="concurrent.futures.process.BrokenProcessPool"><code class="xref py py-exc docutils literal notranslate">BrokenProcessPool</code></a> error is now raised.
Previously, behaviour
was undefined but operations on the executor or its futures would often
freeze or deadlock.
</div>
<div class="versionchanged">
Changed in version 3.7: The mp_context argument was added to allow users to control the
start_method for worker processes created by the pool.
Added the initializer and initargs arguments.
<div class="admonition note">
Note
The default <a class="reference internal" href="multiprocessing.html#module-multiprocessing" title="multiprocessing: Process-based parallelism."><code class="xref py py-mod docutils literal notranslate">multiprocessing</code></a> start method
(see <a class="reference internal" href="multiprocessing.html#multiprocessing-start-methods">Contexts and start methods</a>) will change away from
fork in Python 3.14. Code that requires fork be used for their
<a class="reference internal" href="#concurrent.futures.ProcessPoolExecutor" title="concurrent.futures.ProcessPoolExecutor"><code class="xref py py-class docutils literal notranslate">ProcessPoolExecutor</code></a> should explicitly specify that by
passing a <code class="docutils literal notranslate">mp_context=multiprocessing.get_context(&quot;fork&quot;)</code>
parameter.
</div>
</div>
<div class="versionchanged">
Changed in version 3.11: The max_tasks_per_child argument was added to allow users to
control the lifetime of workers in the pool.
</div>
<div class="versionchanged">
Changed in version 3.12: On POSIX systems, if your application has multiple threads and the
<a class="reference internal" href="multiprocessing.html#module-multiprocessing" title="multiprocessing: Process-based parallelism."><code class="xref py py-mod docutils literal notranslate">multiprocessing</code></a> context uses the <code class="docutils literal notranslate">&quot;fork&quot;</code> start method:
The <a class="reference internal" href="os.html#os.fork" title="os.fork"><code class="xref py py-func docutils literal notranslate">os.fork()</code></a> function called internally to spawn workers may raise a
<a class="reference internal" href="exceptions.html#DeprecationWarning" title="DeprecationWarning"><code class="xref py py-exc docutils literal notranslate">DeprecationWarning</code></a>. Pass a mp_context configured to use a
different start method. See the <a class="reference internal" href="os.html#os.fork" title="os.fork"><code class="xref py py-func docutils literal notranslate">os.fork()</code></a> documentation for
further explanation.
</div>
</dd></dl>

<section id="processpoolexecutor-example">
<h3>ProcessPoolExecutor Example<a class="headerlink" href="#processpoolexecutor-example" title="Link to this heading">¶</a></h3>
<div class="highlight-python3 notranslate"><div class="highlight"><pre>import concurrent.futures
import math

PRIMES = [
 112272535095293,
 112582705942171,
 112272535095293,
 115280095190773,
 115797848077099,
 1099726899285419]

def is_prime(n):
 if n &lt; 2:
 return False
 if n == 2:
 return True
 if n % 2 == 0:
 return False

sqrt_n = int(math.floor(math.sqrt(n)))
 for i in range(3, sqrt_n + 1, 2):
 if n % i == 0:
 return False
 return True

def main():
 with concurrent.futures.ProcessPoolExecutor() as executor:
 for number, prime in zip(PRIMES, executor.map(is_prime, PRIMES)):
 print(&#39;%d is prime: %s&#39; % (number, prime))

if __name__ == &#39;__main__&#39;:
 main()
</pre></div>
</div>
</section>
</section>
<section id="future-objects">
<h2>Future Objects<a class="headerlink" href="#future-objects" title="Link to this heading">¶</a></h2>
The <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> class encapsulates the asynchronous execution of a callable.
<a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> instances are created by <a class="reference internal" href="#concurrent.futures.Executor.submit" title="concurrent.futures.Executor.submit"><code class="xref py py-meth docutils literal notranslate">Executor.submit()</code></a>.
<dl class="py class">
<dt class="sig sig-object py" id="concurrent.futures.Future">
class concurrent.futures.Future<a class="headerlink" href="#concurrent.futures.Future" title="Link to this definition">¶</a></dt>
<dd>Encapsulates the asynchronous execution of a callable. <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a>
instances are created by <a class="reference internal" href="#concurrent.futures.Executor.submit" title="concurrent.futures.Executor.submit"><code class="xref py py-meth docutils literal notranslate">Executor.submit()</code></a> and should not be created
directly except for testing.
<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.cancel">
cancel()<a class="headerlink" href="#concurrent.futures.Future.cancel" title="Link to this definition">¶</a></dt>
<dd>Attempt to cancel the call. If the call is currently being executed or
finished running and cannot be cancelled then the method will return
<code class="docutils literal notranslate">False</code>, otherwise the call will be cancelled and the method will
return <code class="docutils literal notranslate">True</code>.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.cancelled">
cancelled()<a class="headerlink" href="#concurrent.futures.Future.cancelled" title="Link to this definition">¶</a></dt>
<dd>Return <code class="docutils literal notranslate">True</code> if the call was successfully cancelled.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.running">
running()<a class="headerlink" href="#concurrent.futures.Future.running" title="Link to this definition">¶</a></dt>
<dd>Return <code class="docutils literal notranslate">True</code> if the call is currently being executed and cannot be
cancelled.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.done">
done()<a class="headerlink" href="#concurrent.futures.Future.done" title="Link to this definition">¶</a></dt>
<dd>Return <code class="docutils literal notranslate">True</code> if the call was successfully cancelled or finished
running.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.result">
result(timeout=None)<a class="headerlink" href="#concurrent.futures.Future.result" title="Link to this definition">¶</a></dt>
<dd>Return the value returned by the call. If the call hasn’t yet completed
then this method will wait up to timeout seconds. If the call hasn’t
completed in timeout seconds, then a
<a class="reference internal" href="exceptions.html#TimeoutError" title="TimeoutError"><code class="xref py py-exc docutils literal notranslate">TimeoutError</code></a> will be raised. timeout can be
an int or float. If timeout is not specified or <code class="docutils literal notranslate">None</code>, there is no
limit to the wait time.
If the future is cancelled before completing then <a class="reference internal" href="#concurrent.futures.CancelledError" title="concurrent.futures.CancelledError"><code class="xref py py-exc docutils literal notranslate">CancelledError</code></a>
will be raised.
If the call raised an exception, this method will raise the same exception.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.exception">
exception(timeout=None)<a class="headerlink" href="#concurrent.futures.Future.exception" title="Link to this definition">¶</a></dt>
<dd>Return the exception raised by the call. If the call hasn’t yet
completed then this method will wait up to timeout seconds. If the
call hasn’t completed in timeout seconds, then a
<a class="reference internal" href="exceptions.html#TimeoutError" title="TimeoutError"><code class="xref py py-exc docutils literal notranslate">TimeoutError</code></a> will be raised. timeout can be
an int or float. If timeout is not specified or <code class="docutils literal notranslate">None</code>, there is no
limit to the wait time.
If the future is cancelled before completing then <a class="reference internal" href="#concurrent.futures.CancelledError" title="concurrent.futures.CancelledError"><code class="xref py py-exc docutils literal notranslate">CancelledError</code></a>
will be raised.
If the call completed without raising, <code class="docutils literal notranslate">None</code> is returned.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.add_done_callback">
add_done_callback(fn)<a class="headerlink" href="#concurrent.futures.Future.add_done_callback" title="Link to this definition">¶</a></dt>
<dd>Attaches the callable fn to the future. fn will be called, with the
future as its only argument, when the future is cancelled or finishes
running.
Added callables are called in the order that they were added and are
always called in a thread belonging to the process that added them. If
the callable raises an <a class="reference internal" href="exceptions.html#Exception" title="Exception"><code class="xref py py-exc docutils literal notranslate">Exception</code></a> subclass, it will be logged and
ignored. If the callable raises a <a class="reference internal" href="exceptions.html#BaseException" title="BaseException"><code class="xref py py-exc docutils literal notranslate">BaseException</code></a> subclass, the
behavior is undefined.
If the future has already completed or been cancelled, fn will be
called immediately.
</dd></dl>

The following <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> methods are meant for use in unit tests and
<a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> implementations.
<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.set_running_or_notify_cancel">
set_running_or_notify_cancel()<a class="headerlink" href="#concurrent.futures.Future.set_running_or_notify_cancel" title="Link to this definition">¶</a></dt>
<dd>This method should only be called by <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> implementations
before executing the work associated with the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> and by unit
tests.
If the method returns <code class="docutils literal notranslate">False</code> then the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> was cancelled,
i.e. <a class="reference internal" href="#concurrent.futures.Future.cancel" title="concurrent.futures.Future.cancel"><code class="xref py py-meth docutils literal notranslate">Future.cancel()</code></a> was called and returned <code class="docutils literal notranslate">True</code>. Any threads
waiting on the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> completing (i.e. through
<a class="reference internal" href="#concurrent.futures.as_completed" title="concurrent.futures.as_completed"><code class="xref py py-func docutils literal notranslate">as_completed()</code></a> or <a class="reference internal" href="#concurrent.futures.wait" title="concurrent.futures.wait"><code class="xref py py-func docutils literal notranslate">wait()</code></a>) will be woken up.
If the method returns <code class="docutils literal notranslate">True</code> then the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> was not cancelled
and has been put in the running state, i.e. calls to
<a class="reference internal" href="#concurrent.futures.Future.running" title="concurrent.futures.Future.running"><code class="xref py py-meth docutils literal notranslate">Future.running()</code></a> will return <code class="docutils literal notranslate">True</code>.
This method can only be called once and cannot be called after
<a class="reference internal" href="#concurrent.futures.Future.set_result" title="concurrent.futures.Future.set_result"><code class="xref py py-meth docutils literal notranslate">Future.set_result()</code></a> or <a class="reference internal" href="#concurrent.futures.Future.set_exception" title="concurrent.futures.Future.set_exception"><code class="xref py py-meth docutils literal notranslate">Future.set_exception()</code></a> have been
called.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.set_result">
set_result(result)<a class="headerlink" href="#concurrent.futures.Future.set_result" title="Link to this definition">¶</a></dt>
<dd>Sets the result of the work associated with the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> to
result.
This method should only be used by <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> implementations and
unit tests.
<div class="versionchanged">
Changed in version 3.8: This method raises
<a class="reference internal" href="#concurrent.futures.InvalidStateError" title="concurrent.futures.InvalidStateError"><code class="xref py py-exc docutils literal notranslate">concurrent.futures.InvalidStateError</code></a> if the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> is
already done.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="concurrent.futures.Future.set_exception">
set_exception(exception)<a class="headerlink" href="#concurrent.futures.Future.set_exception" title="Link to this definition">¶</a></dt>
<dd>Sets the result of the work associated with the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> to the
<a class="reference internal" href="exceptions.html#Exception" title="Exception"><code class="xref py py-class docutils literal notranslate">Exception</code></a> exception.
This method should only be used by <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> implementations and
unit tests.
<div class="versionchanged">
Changed in version 3.8: This method raises
<a class="reference internal" href="#concurrent.futures.InvalidStateError" title="concurrent.futures.InvalidStateError"><code class="xref py py-exc docutils literal notranslate">concurrent.futures.InvalidStateError</code></a> if the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> is
already done.
</div>
</dd></dl>

</dd></dl>

</section>
<section id="module-functions">
<h2>Module Functions<a class="headerlink" href="#module-functions" title="Link to this heading">¶</a></h2>
<dl class="py function">
<dt class="sig sig-object py" id="concurrent.futures.wait">
concurrent.futures.wait(fs, timeout=None, return_when=ALL_COMPLETED)<a class="headerlink" href="#concurrent.futures.wait" title="Link to this definition">¶</a></dt>
<dd>Wait for the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> instances (possibly created by different
<a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> instances) given by fs to complete. Duplicate futures
given to fs are removed and will be returned only once. Returns a named
2-tuple of sets. The first set, named <code class="docutils literal notranslate">done</code>, contains the futures that
completed (finished or cancelled futures) before the wait completed. The
second set, named <code class="docutils literal notranslate">not_done</code>, contains the futures that did not complete
(pending or running futures).
timeout can be used to control the maximum number of seconds to wait before
returning. timeout can be an int or float. If timeout is not specified
or <code class="docutils literal notranslate">None</code>, there is no limit to the wait time.
return_when indicates when this function should return. It must be one of
the following constants:
<table class="docutils align-default">
<thead>
<tr class="row-odd"><th class="head">Constant</th>
<th class="head">Description</th>
</tr>
</thead>
<tbody>
<tr class="row-even"><td><dl class="py data">
<dt class="sig sig-object py" id="concurrent.futures.FIRST_COMPLETED">
concurrent.futures.FIRST_COMPLETED<a class="headerlink" href="#concurrent.futures.FIRST_COMPLETED" title="Link to this definition">¶</a></dt>
<dd></dd></dl>

</td>
<td>The function will return when any future finishes or is cancelled.</td>
</tr>
<tr class="row-odd"><td><dl class="py data">
<dt class="sig sig-object py" id="concurrent.futures.FIRST_EXCEPTION">
concurrent.futures.FIRST_EXCEPTION<a class="headerlink" href="#concurrent.futures.FIRST_EXCEPTION" title="Link to this definition">¶</a></dt>
<dd></dd></dl>

</td>
<td>The function will return when any future finishes by raising an
exception. If no future raises an exception
then it is equivalent to <a class="reference internal" href="#concurrent.futures.ALL_COMPLETED" title="concurrent.futures.ALL_COMPLETED"><code class="xref py py-const docutils literal notranslate">ALL_COMPLETED</code></a>.</td>
</tr>
<tr class="row-even"><td><dl class="py data">
<dt class="sig sig-object py" id="concurrent.futures.ALL_COMPLETED">
concurrent.futures.ALL_COMPLETED<a class="headerlink" href="#concurrent.futures.ALL_COMPLETED" title="Link to this definition">¶</a></dt>
<dd></dd></dl>

</td>
<td>The function will return when all futures finish or are cancelled.</td>
</tr>
</tbody>
</table>
</dd></dl>

<dl class="py function">
<dt class="sig sig-object py" id="concurrent.futures.as_completed">
concurrent.futures.as_completed(fs, timeout=None)<a class="headerlink" href="#concurrent.futures.as_completed" title="Link to this definition">¶</a></dt>
<dd>Returns an iterator over the <a class="reference internal" href="#concurrent.futures.Future" title="concurrent.futures.Future"><code class="xref py py-class docutils literal notranslate">Future</code></a> instances (possibly created by
different <a class="reference internal" href="#concurrent.futures.Executor" title="concurrent.futures.Executor"><code class="xref py py-class docutils literal notranslate">Executor</code></a> instances) given by fs that yields futures as
they complete (finished or cancelled futures). Any futures given by fs that
are duplicated will be returned once. Any futures that completed before
<a class="reference internal" href="#concurrent.futures.as_completed" title="concurrent.futures.as_completed"><code class="xref py py-func docutils literal notranslate">as_completed()</code></a> is called will be yielded first. The returned iterator
raises a <a class="reference internal" href="exceptions.html#TimeoutError" title="TimeoutError"><code class="xref py py-exc docutils literal notranslate">TimeoutError</code></a> if <a class="reference internal" href="stdtypes.html#iterator.__next__" title="iterator.__next__"><code class="xref py py-meth docutils literal notranslate">__next__()</code></a>
is called and the result isn’t available after timeout seconds from the
original call to <a class="reference internal" href="#concurrent.futures.as_completed" title="concurrent.futures.as_completed"><code class="xref py py-func docutils literal notranslate">as_completed()</code></a>. timeout can be an int or float. If
timeout is not specified or <code class="docutils literal notranslate">None</code>, there is no limit to the wait time.
</dd></dl>

<div class="admonition seealso">
See also
<dl class="simple">
<dt><a class="pep reference external" href="https://peps.python.org/pep-3148/">PEP 3148</a> – futures - execute computations asynchronously</dt><dd>The proposal which described this feature for inclusion in the Python
standard library.
</dd>
</dl>
</div>
</section>
<section id="exception-classes">
<h2>Exception classes<a class="headerlink" href="#exception-classes" title="Link to this heading">¶</a></h2>
<dl class="py exception">
<dt class="sig sig-object py" id="concurrent.futures.CancelledError">
exception concurrent.futures.CancelledError<a class="headerlink" href="#concurrent.futures.CancelledError" title="Link to this definition">¶</a></dt>
<dd>Raised when a future is cancelled.
</dd></dl>

<dl class="py exception">
<dt class="sig sig-object py" id="concurrent.futures.TimeoutError">
exception concurrent.futures.TimeoutError<a class="headerlink" href="#concurrent.futures.TimeoutError" title="Link to this definition">¶</a></dt>
<dd>A deprecated alias of <a class="reference internal" href="exceptions.html#TimeoutError" title="TimeoutError"><code class="xref py py-exc docutils literal notranslate">TimeoutError</code></a>,
raised when a future operation exceeds the given timeout.
<div class="versionchanged">
Changed in version 3.11: This class was made an alias of <a class="reference internal" href="exceptions.html#TimeoutError" title="TimeoutError"><code class="xref py py-exc docutils literal notranslate">TimeoutError</code></a>.
</div>
</dd></dl>

<dl class="py exception">
<dt class="sig sig-object py" id="concurrent.futures.BrokenExecutor">
exception concurrent.futures.BrokenExecutor<a class="headerlink" href="#concurrent.futures.BrokenExecutor" title="Link to this definition">¶</a></dt>
<dd>Derived from <a class="reference internal" href="exceptions.html#RuntimeError" title="RuntimeError"><code class="xref py py-exc docutils literal notranslate">RuntimeError</code></a>, this exception class is raised
when an executor is broken for some reason, and cannot be used
to submit or execute new tasks.
<div class="versionadded">
New in version 3.7.
</div>
</dd></dl>

<dl class="py exception">
<dt class="sig sig-object py" id="concurrent.futures.InvalidStateError">
exception concurrent.futures.InvalidStateError<a class="headerlink" href="#concurrent.futures.InvalidStateError" title="Link to this definition">¶</a></dt>
<dd>Raised when an operation is performed on a future that is not allowed
in the current state.
<div class="versionadded">
New in version 3.8.
</div>
</dd></dl>

<dl class="py exception">
<dt class="sig sig-object py" id="concurrent.futures.thread.BrokenThreadPool">
exception concurrent.futures.thread.BrokenThreadPool<a class="headerlink" href="#concurrent.futures.thread.BrokenThreadPool" title="Link to this definition">¶</a></dt>
<dd>Derived from <a class="reference internal" href="#concurrent.futures.BrokenExecutor" title="concurrent.futures.BrokenExecutor"><code class="xref py py-exc docutils literal notranslate">BrokenExecutor</code></a>, this exception
class is raised when one of the workers
of a <a class="reference internal" href="#concurrent.futures.ThreadPoolExecutor" title="concurrent.futures.ThreadPoolExecutor"><code class="xref py py-class docutils literal notranslate">ThreadPoolExecutor</code></a>
has failed initializing.
<div class="versionadded">
New in version 3.7.
</div>
</dd></dl>

<dl class="py exception">
<dt class="sig sig-object py" id="concurrent.futures.process.BrokenProcessPool">
exception concurrent.futures.process.BrokenProcessPool<a class="headerlink" href="#concurrent.futures.process.BrokenProcessPool" title="Link to this definition">¶</a></dt>
<dd>Derived from <a class="reference internal" href="#concurrent.futures.BrokenExecutor" title="concurrent.futures.BrokenExecutor"><code class="xref py py-exc docutils literal notranslate">BrokenExecutor</code></a> (formerly
<a class="reference internal" href="exceptions.html#RuntimeError" title="RuntimeError"><code class="xref py py-exc docutils literal notranslate">RuntimeError</code></a>), this exception class is raised when one of the
workers of a <a class="reference internal" href="#concurrent.futures.ProcessPoolExecutor" title="concurrent.futures.ProcessPoolExecutor"><code class="xref py py-class docutils literal notranslate">ProcessPoolExecutor</code></a>
has terminated in a non-clean
fashion (for example, if it was killed from the outside).
<div class="versionadded">
New in version 3.3.
</div>
</dd></dl>

</section>
</section>

<div class="clearer"></div>
 </div>
 </div>
 </div>
 <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
 <div class="sphinxsidebarwrapper">
 <div>
 <h3><a href="../contents.html">Table of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#"><code class="xref py py-mod docutils literal notranslate">concurrent.futures</code> — Launching parallel tasks</a><ul>
<li><a class="reference internal" href="#executor-objects">Executor Objects</a></li>
<li><a class="reference internal" href="#threadpoolexecutor">ThreadPoolExecutor</a><ul>
<li><a class="reference internal" href="#threadpoolexecutor-example">ThreadPoolExecutor Example</a></li>
</ul>
</li>
<li><a class="reference internal" href="#processpoolexecutor">ProcessPoolExecutor</a><ul>
<li><a class="reference internal" href="#processpoolexecutor-example">ProcessPoolExecutor Example</a></li>
</ul>
</li>
<li><a class="reference internal" href="#future-objects">Future Objects</a></li>
<li><a class="reference internal" href="#module-functions">Module Functions</a></li>
<li><a class="reference internal" href="#exception-classes">Exception classes</a></li>
</ul>
</li>
</ul>

</div>
 <div class="clearer"></div>
 </div> 
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 >index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="subprocess.html" title="subprocess — Subprocess management"
 >next</a> |</li>
 <li class="right" >
 <a href="concurrent.html" title="The concurrent package"
 >previous</a> |</li>

<li class="nav-item nav-item-1"><a href="index.html" >The Python Standard Library</a> &#187;</li>
 <li class="nav-item nav-item-2"><a href="concurrency.html" >Concurrent Execution</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href=""><code class="xref py py-mod docutils literal notranslate">concurrent.futures</code> — Launching parallel tasks</a></li>
 <li class="right">

<div class="inline-search" role="search">
 <form class="inline-search" action="../search.html" method="get">
 <input placeholder="Quick search" aria-label="Quick search" type="search" name="q" id="search-box" />
 <input type="submit" value="Go" />
 </form>
 </div>
 |
 </li>
 <li class="right">
<label class="theme-selector-label">
 Theme
 <select class="theme-selector" oninput="activateTheme(this.value)">
 <option value="auto" selected>Auto</option>
 <option value="light">Light</option>
 <option value="dark">Dark</option>
 </select>
</label> |</li>
 
 </ul>
 </div> 
 <div class="footer">
 &copy; 
 <a href="../copyright.html">
 
 Copyright
 
 </a>
 2001-2024, Python Software Foundation.
 
 This page is licensed under the Python Software Foundation License Version 2.
 
 Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License.
 
 
 See <a href="/license.html">History and License</a> for more information.

The Python Software Foundation is a non-profit corporation.
<a href="https://www.python.org/psf/donations/">Please donate.</a>
 
 
 Last updated on Apr 09, 2024 (13:47 UTC).
 
 <a href="/bugs.html">Found a bug</a>?

Created using <a href="https://www.sphinx-doc.org/">Sphinx</a> 7.2.6.
 </div>

</body>
</html>