Message 302751 - Python tracker

Message302751

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	<1506094887.79.0.442970788808.issue31452@psf.upfronthosting.co.za>
In-reply-to

Content
> 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.

Content

> 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.

History
Date	User	Action	Args
2017-09-22 15:41:27	gvanrossum	set	recipients: + gvanrossum, asvetlov, yselivanov, kwarunek, Andrew Lytvyn
2017-09-22 15:41:27	gvanrossum	set	messageid: <1506094887.79.0.442970788808.issue31452@psf.upfronthosting.co.za>
2017-09-22 15:41:27	gvanrossum	link	issue31452 messages
2017-09-22 15:41:27	gvanrossum	create