summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbrian.quinlan <devnull@localhost>2009-10-16 02:44:02 +0000
committerbrian.quinlan <devnull@localhost>2009-10-16 02:44:02 +0000
commit7d43f0e1c58adb68067a3f2cb21598fb625446b8 (patch)
treeec0125341babf169a0faf62fb407faf91b9f24b3
parent180b100e21b97cab7af74be7bfb17c6713772a2d (diff)
downloadfutures-7d43f0e1c58adb68067a3f2cb21598fb625446b8.tar.gz
Add a section pointing to the reference implementation
-rw-r--r--PEP.txt15
1 files changed, 15 insertions, 0 deletions
diff --git a/PEP.txt b/PEP.txt
index 4eec5e0..60e487e 100644
--- a/PEP.txt
+++ b/PEP.txt
@@ -313,6 +313,17 @@ 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.
+========================
+Reference Implementation
+========================
+
+The reference implementation [5]_ contains a complete and tested implementation
+of a thread-based `Executor` based on the proposed design. It also includes a
+process-based `Executor` implementation that is largely complete but can deadlock
+in certain cases. These cases are not currently well understood and must be
+resolved before the process-based implementation can be considered for
+inclusion.
+
==========
References
==========
@@ -338,6 +349,10 @@ References
`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`
+.. [5]
+
+ Reference `futures` implementation `http://code.google.com/p/pythonfutures`
+
=========
Copyright
=========