[Python-checkins] peps: Get rid of Future.running(); see bug 18699.

[guido.van.rossum]

http://hg.python.org/peps/rev/922c0fe6ebee
changeset:   5047:922c0fe6ebee
user:        Guido van Rossum <guido at python.org>
date:        Fri Aug 09 17:26:53 2013 -0700
summary:
  Get rid of Future.running(); see bug 18699.

files:
  pep-3156.txt |  8 +++-----
  1 files changed, 3 insertions(+), 5 deletions(-)


diff --git a/pep-3156.txt b/pep-3156.txt
--- a/pep-3156.txt
+++ b/pep-3156.txt
@@ -728,7 +728,7 @@
   ``sig`` must be a valid sigal number defined in the ``signal``
   module.  If the signal cannot be handled this raises an exception:
   ``ValueError`` if it is not a valid signal or if it is an
-  uncatchable signale (e.g. ``SIGKILL``), ``RuntimeError`` if this
+  uncatchable signal (e.g. ``SIGKILL``), ``RuntimeError`` if this
   particular event loop instance cannot handle signals (since signals
   are global per process, only an event loop associated with the main
   thread can handle signals).
@@ -817,9 +817,6 @@
 
 - ``cancelled()``.  Returns ``True`` if the Future was cancelled.
 
-- ``running()``.  Always returns ``False``.  Difference with PEP 3148:
-  there is no "running" state.
-
 - ``done()``.  Returns ``True`` if the Future is done.  Note that a
   cancelled Future is considered done too (here and everywhere).
 
@@ -861,7 +858,8 @@
   callbacks.  Difference with PEP 3148: This is a public API.
 
 The internal method ``set_running_or_notify_cancel()`` is not
-supported; there is no way to set the running state.
+supported; there is no way to set the running state.  Likewise,
+the method ``running()`` is not supported.
 
 The following exceptions are defined:
 

-- 
Repository URL: http://hg.python.org/peps