summaryrefslogtreecommitdiff
path: root/PEP.txt
blob: 4eec5e0f9bae1a1ab72ec8bbbe72df6363ac1b1d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
PEP:               XXX
Title:             Standard futures library
Version:           $Revision$
Last-Modified:     $Date$
Author:            Brian Quinlan <brian@sweetapp.com>
Status:            Draft
Type:              Standards Track
Content-Type:      text/x-rst
Created:           16-Oct-2009
Python-Version:    3.2
Post-History:

========
Abstract
========

This PEP proposes a design for a package that facilitates the evaluation of
callables using threads.

==========
Motivation
==========

Python currently has powerful primitives to construct multi-threaded
applications but parallelizing simple operations requires a lot of work i.e.
explicitly launching threads, constructing a work/results queue, and waiting
for completion or some other termination condition (e.g. failure, timeout). It
is also difficult to design an application with a global thread limit when each
component invents its own threading stategy.

=============
Specification
=============

Example
-------

::

    import functools
    import urllib.request
    import futures
    
    URLS = ['http://www.foxnews.com/',
            'http://www.cnn.com/',
            'http://europe.wsj.com/',
            'http://www.bbc.co.uk/',
            'http://some-made-up-domain.com/']
    
    def load_url(url, timeout):
        return urllib.request.urlopen(url, timeout=timeout).read()
    
    with futures.ThreadPoolExecutor(max_threads=5) as executor:
       future_list = executor.run_to_futures(
               [functools.partial(load_url, url, 30) for url in URLS])
    
    for url, future in zip(URLS, future_list):
        if future.exception() is not None:
            print('%r generated an exception: %s' % (url, future.exception()))
        else:
            print('%r page is %d bytes' % (url, len(future.result())))

Interface
---------

The proposed package provides three core class: `Executors`, `FutureLists` and
`Futures`.

Executor
''''''''

`Executor` is an abstract class that provides methods to execute calls
asynchronously.

`run_to_futures(calls, timeout=None, return_when=ALL_COMPLETED)`

Schedule the given calls for execution and return a `FutureList`
containing a `Future` for each call. This method should always be
called using keyword arguments, which are:

*calls* must be a sequence of callables that take no arguments.

*timeout* can be used to control the maximum number of seconds to wait before
returning. If *timeout* is not specified or ``None`` then there is no limit
to the wait time.

*return_when* indicates when the method should return. It must be one of the
following constants:

============================= ==================================================
 Constant                      Description
============================= ==================================================
`FIRST_COMPLETED`             The method will return when any call finishes.
`FIRST_EXCEPTION`             The method will return when any call raises an
                              exception or when all calls finish.
`ALL_COMPLETED`               The method will return when all calls finish.
`RETURN_IMMEDIATELY`          The method will return immediately.
============================= ==================================================

`run_to_results(calls, timeout=None)`

Schedule the given calls for execution and return an iterator over their
results. The returned iterator raises a `TimeoutError` if `__next__()` is called
and the result isn't available after *timeout* seconds from the original call to
`run_to_results()`. If *timeout* is not specified or ``None`` then there is no
limit to the wait time. If a call raises an exception then that exception will
be raised when its value is retrieved from the iterator.

`map(func, *iterables, timeout=None)`

Equivalent to map(*func*, *\*iterables*) but executed asynchronously and
possibly out-of-order. The returned iterator raises a `TimeoutError` if
`__next__()` is called and the result isn't available after *timeout* seconds
from the original call to `run_to_results()`. If *timeout* is not specified or
``None`` then there is no limit to the wait time. If a call raises an exception
then that exception will be raised when its value is retrieved from the iterator.

`Executor.shutdown()`

Signal the executor that it should free any resources that it is using when
the currently pending futures are done executing. Calls to
`Executor.run_to_futures`, `Executor.run_to_results` and
`Executor.map` made after shutdown will raise `RuntimeError`.

ThreadPoolExecutor
''''''''''''''''''

The `ThreadPoolExecutor` class is an `Executor` subclass that uses a pool of
threads to execute calls asynchronously.

`__init__(max_threads)`

Executes calls asynchronously using at pool of at most *max_threads* threads.

FutureList Objects
''''''''''''''''''

The `FutureList` class is an immutable container for `Future` instances and
should only be instantiated by `Executor.run_to_futures`.

`wait(timeout=None, return_when=ALL_COMPLETED)`

Wait until the given conditions are met. This method should always be called
using keyword arguments, which are:

*timeout* can be used to control the maximum number of seconds to wait before
returning. If *timeout* is not specified or ``None`` then there is no limit
to the wait time.

*return_when* indicates when the method should return. It must be one of the
following constants:

============================= ==================================================
 Constant                      Description                            
============================= ==================================================
`FIRST_COMPLETED`             The method will return when any call finishes.
`FIRST_EXCEPTION`             The method will return when any call raises an
                              exception or when all calls finish.
`ALL_COMPLETED`               The method will return when all calls finish.
`RETURN_IMMEDIATELY`          The method will return immediately.
                              This option is only available for consistency with
                              `Executor.run_to_results` and is not likely to be
                              useful.
============================= ==================================================

`cancel(timeout=None)`

Cancel every `Future` in the list and wait up to *timeout* seconds for
them to be cancelled or, if any are already running, to finish. Raises a
`TimeoutError` if the running calls do not complete before the timeout.
If *timeout* is not specified or ``None`` then there is no limit to the wait
time.

`has_running_futures()`

Return `True` if any `Future` in the list is currently executing.

`has_cancelled_futures()`

Return `True` if any `Future` in the list was successfully cancelled.

`has_done_futures()`

Return `True` if any `Future` in the list has completed or was successfully
cancelled.

`has_successful_futures()`

Return `True` if any `Future` in the list has completed without raising an
exception.

`has_exception_futures()`

Return `True` if any `Future` in the list completed by raising an
exception.

`cancelled_futures()`

Return an iterator over all `Future` instances that were successfully
cancelled.

`done_futures()`

Return an iterator over all `Future` instances that completed are were cancelled.

`successful_futures()`

Return an iterator over all `Future` instances that completed without raising an
exception.

`exception_futures()`

Return an iterator over all `Future` instances that completed by raising an
exception.

`running_futures()`

Return an iterator over all `Future` instances that are currently executing.

`__len__()`

Return the number of futures in the `FutureList`.

`__getitem__(i)`

Return the ith `Future` in the list. The order of the futures in the
`FutureList` matches the order of the class passed to
`Executor.run_to_futures`

`FutureList.__contains__(future)`

Return `True` if *future* is in the `FutureList`.

Future Objects
''''''''''''''

The `Future` class encapulates the asynchronous execution of a function
or method call. `Future` instances are created by the
`Executor.run_to_futures` and bundled into a `FutureList`.

`cancel()`

Attempt to cancel the call. If the call is currently being executed then
it cannot be cancelled and the method will return `False`, otherwise the call
will be cancelled and the method will return `True`.

`Future.cancelled()`

Return `True` if the call was successfully cancelled.

`Future.done()`

Return `True` if the call was successfully cancelled or finished running.

`result(timeout=None)`

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 `TimeoutError` will be raised. If *timeout*
is not specified or ``None`` then there is no limit to the wait time.

If the future is cancelled before completing then `CancelledError` will
be raised.

If the call raised then this method will raise the same exception.

`exception(timeout=None)`

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 `TimeoutError` will be raised.
If *timeout* is not specified or ``None`` then there is no limit to the wait
time.

If the future is cancelled before completing then `CancelledError` will
be raised.

If the call completed without raising then ``None`` is returned.   

`index`

int indicating the index of the future in its `FutureList`.

=========
Rationale
=========

The proposed design of this module was heavily influenced by the the Java
java.util.concurrent package [1]_. The conceptual basis of the module, as in
Java, is the Future class, which represents the progress and results of an
asynchronous computation. The Future class makes little committement to the
evaluation mode being used e.g. it can be be used to represent lazy or eager
evaluation, for evaluation using threads or using processes.

Futures are created by concrete implementations of the Executor class
(called ExecutorService in Java). The reference implementation provides
a class that uses a thread pool to eagerly evaluate computations and a
prototype implementation of a class that uses a process pool but the
design is flexible enough to accomodate other execution strategies.

Futures have already been seen in Python as part of a popular Python
cookbook recipe [2]_ and have discussed on the Python-3000 mailing list [3]_.

The proposed design is explicit i.e. it requires that clients be aware that
they are consuming Futures. It would be possible to design a module that
would return proxy objects (in the style of `weakref`) that could be used
transparently. It is possible to build a proxy implementation on top of
the proposed explicit mechanism.

The proposed design does not introduce any changes to Python language syntax
or semantics. Special syntax could be introduced [4]_ to mark function and
method calls as asynchronous. A proxy result would be returned while the
operation is eagerly evaluated asynchronously, and execution would only
block if the proxy object were used before the operation completed.

==========  
References
==========

..  [1]

    `java.util.concurrent` package documentation
    `http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/package-summary.html`

..  [2]

    Pythono Cookbook recipe 84317, "Easy threading with Futures"
    `http://code.activestate.com/recipes/84317/`

..  [3]

    `Python-3000` thread, "mechanism for handling asynchronous concurrency"
    `http://mail.python.org/pipermail/python-3000/2006-April/000960.html`


..  [4]

    `Python 3000` thread, "Futures in Python 3000 (was Re: mechanism for handling asynchronous concurrency)"
    `http://mail.python.org/pipermail/python-3000/2006-April/000970.html`

=========
Copyright
=========

This document has been placed in the public domain.



..
   Local Variables:
   mode: indented-text
   indent-tabs-mode: nil
   sentence-end-double-space: t
   fill-column: 70
   coding: utf-8
   End: