[Python-checkins] peps: Clarify exactly how vague the spec for stop() really is.

[guido.van.rossum]

http://hg.python.org/peps/rev/98eb80da3c9f
changeset:   4821:98eb80da3c9f
user:        Guido van Rossum <guido at python.org>
date:        Sun Mar 24 17:48:02 2013 -0700
summary:
  Clarify exactly how vague the spec for stop() really is.

files:
  pep-3156.txt |  9 +++++++--
  1 files changed, 7 insertions(+), 2 deletions(-)


diff --git a/pep-3156.txt b/pep-3156.txt
--- a/pep-3156.txt
+++ b/pep-3156.txt
@@ -221,8 +221,13 @@
 - ``stop()``.  Stops the event loop as soon as it is convenient.  It
   is fine to restart the loop with ``run()`` or ``run_until_complete()``
   subsequently; no scheduled callbacks will be lost if this happens.
-
-  Note: How soon the event loop stops is up to the implementation.
+  Note: ``stop()`` returns normally and the current callback is
+  allowed to continue.  How soon after this point the event loop stops
+  is up to the implementation, but the intention is to stop short of
+  polling for I/O, and not to run any callbacks scheduled in the
+  future; the major freedom an implementation has is how much of the
+  "ready queue" (callbacks already scheduled with ``call_soon()``) it
+  processes before stopping.
 
 - ``close()``.  Closes the event loop, releasing any resources it may
   hold, such as the file descriptor used by ``epoll()`` or

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