Message 386488 - Python tracker

➜

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	spenczar
Recipients	asvetlov, kj, spenczar, yselivanov
Date	2021-02-04.17:49:27
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1612460967.93.0.938832079405.issue43119@roundup.psfhosted.org>
In-reply-to

Content
Thanks for testing on more Python versions. Yes, adding asyncio.sleep(0) after each put is an effective workaround - it's certainly possible to manually yield like that. I just think that that's what asyncio.Queue.put ought to be doing - in fact, that's my proposed change in the associated PR: https://github.com/python/cpython/pull/24433/files#diff-22a6bcb03e783378149a3e9411c185b13c908e61886ffd55145634b7ab12caacR141 I suppose that, more broadly, I would have expected that _any_ `await f()` call would be a preemptible point, but I think that's a much, much larger discussion.

Thanks for testing on more Python versions.

Yes, adding asyncio.sleep(0) after each put is an effective workaround - it's certainly possible to manually yield like that. I just think that that's what asyncio.Queue.put ought to be doing - in fact, that's my proposed change in the associated PR: https://github.com/python/cpython/pull/24433/files#diff-22a6bcb03e783378149a3e9411c185b13c908e61886ffd55145634b7ab12caacR141

I suppose that, more broadly, I would have expected that _any_ `await f()` call would be a preemptible point, but I think that's a much, much larger discussion.

History
Date	User	Action	Args
2021-02-04 17:49:27	spenczar	set	recipients: + spenczar, asvetlov, yselivanov, kj
2021-02-04 17:49:27	spenczar	set	messageid: <1612460967.93.0.938832079405.issue43119@roundup.psfhosted.org>
2021-02-04 17:49:27	spenczar	link	issue43119 messages
2021-02-04 17:49:27	spenczar	create