You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2014-12-02.16:53:13.901>created_at=<Date2014-09-23.23:46:15.397>labels= ['type-bug', 'docs', 'expert-asyncio']
title='The gloss on asyncio "future with run_forever" example is confusing'updated_at=<Date2014-12-02.16:54:03.192>user='https://github.com/bitdancer'
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.
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!
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: