Get rid of Future.running(); see bug 18699.

This commit is contained in:
Guido van Rossum 2013-08-09 17:26:53 -07:00
parent 31c754206a
commit 003c30d64f
1 changed files with 3 additions and 5 deletions

View File

@ -728,7 +728,7 @@ Signal callbacks
``sig`` must be a valid sigal number defined in the ``signal`` ``sig`` must be a valid sigal number defined in the ``signal``
module. If the signal cannot be handled this raises an exception: module. If the signal cannot be handled this raises an exception:
``ValueError`` if it is not a valid signal or if it is an ``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 particular event loop instance cannot handle signals (since signals
are global per process, only an event loop associated with the main are global per process, only an event loop associated with the main
thread can handle signals). thread can handle signals).
@ -817,9 +817,6 @@ public API is as follows, indicating the differences with PEP 3148:
- ``cancelled()``. Returns ``True`` if the Future was cancelled. - ``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 - ``done()``. Returns ``True`` if the Future is done. Note that a
cancelled Future is considered done too (here and everywhere). cancelled Future is considered done too (here and everywhere).
@ -861,7 +858,8 @@ public API is as follows, indicating the differences with PEP 3148:
callbacks. Difference with PEP 3148: This is a public API. callbacks. Difference with PEP 3148: This is a public API.
The internal method ``set_running_or_notify_cancel()`` is not 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: The following exceptions are defined: