[issue22473] The gloss on asyncio "future with run_forever" example is confusing

STINNER Victor added the comment: I rephrase the explanation of the example and I removed the useless note. Thanks for your feedback David. Don't hesitate to propose other enhancements to the documentation! -- ___ Python tracker

[issue22473] The gloss on asyncio "future with run_forever" example is confusing

Roundup Robot added the comment: New changeset a4b58e779a16 by Victor Stinner in branch '3.4': Close #22473: asyncio doc: rephrase Future with run_forever() example https://hg.python.org/cpython/rev/a4b58e779a16 -- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open

[issue22473] The gloss on asyncio "future with run_forever" example is confusing

Changes by STINNER Victor : -- components: +asyncio ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue22473] The gloss on asyncio "future with run_forever" example is confusing

STINNER Victor added the comment: "But that isn't quite true. It is the callback associated with the future that is displaying the result and stopping the loop." I wrote this example to show that setting the result of a future can schedule a callback. I mean something like: "In this example,

[issue22473] The gloss on asyncio "future with run_forever" example is confusing

Changes by Antoine Pitrou : -- nosy: +giampaolo.rodola, gvanrossum, haypo, pitrou, yselivanov ___ Python tracker ___ ___ Python-bugs-l

[issue22473] The gloss on asyncio "future with run_forever" example is confusing

New submission from R. David Murray: 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 e