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 gvanrossum
Recipients Andrew Lytvyn, asvetlov, gvanrossum, kwarunek, yselivanov
Date 2017-09-22.15:41:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> if you change run_forever with run_until_complete, then behavior changes: success_coro(5) will not be executed

Oh, that's a red herring. The reason is that the event loop stops when you use run_complete(), but the execution of success_coro(5) is still pending, and when you resume the loop (e.g. call run_until_complete() on the same loop with a different task) it will run.

So the issue is really the semantics of gather(), and I agree with Yury that we designed it intentionally that way, and if you want different behavior we'll have to provide a different API.
Date User Action Args
2017-09-22 15:41:27gvanrossumsetrecipients: + gvanrossum, asvetlov, yselivanov, kwarunek, Andrew Lytvyn
2017-09-22 15:41:27gvanrossumsetmessageid: <>
2017-09-22 15:41:27gvanrossumlinkissue31452 messages
2017-09-22 15:41:27gvanrossumcreate