This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients docs@python, r.david.murray
Date 2014-09-23.23:46:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1411515975.42.0.282827755318.issue22473@psf.upfronthosting.co.za>
In-reply-to
Content
In https://docs.python.org/3/library/asyncio-task.html#example-future-with-run-forever we have the sentence

  In this example, the future is responsible to display the result and to stop the loop.

We could dune up the English by rewriting it:

  In this example, the future is responsible for displaying the result and stopping the loop.

But that isn't quite true.  It is the callback associated with the future that is displaying the result and stopping the loop.  So, perhaps the correct gloss is:

  In this example, the got_result callback is responsible for displaying the result and stopping the loop.
History
Date User Action Args
2014-09-23 23:46:15r.david.murraysetrecipients: + r.david.murray, docs@python
2014-09-23 23:46:15r.david.murraysetmessageid: <1411515975.42.0.282827755318.issue22473@psf.upfronthosting.co.za>
2014-09-23 23:46:15r.david.murraylinkissue22473 messages
2014-09-23 23:46:15r.david.murraycreate