Message 362671 - Python tracker

Message362671

Author	yselivanov
Recipients	abacabadabacaba, asvetlov, lukasz.langa, ned.deily, yselivanov
Date	2020-02-25.23:38:53
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1582673934.79.0.418050528066.issue30064@roundup.psfhosted.org>
In-reply-to

Content
> I very doubt if any sane code is organizing like this test: start delayed reading, cancel it and read again. Hm, cancellation should work correctly no matter how "sane" or "insane" the user code is. > The worse, neither previous not current sock_read() implementation doesn't prevent the concurrent reading which basically delivers data in an unpredictable order. But we're not discussing using a socket concurrently -- asyncio explicitly does not support that for the sock_ api. AFAICT this issue is about consequent cancel operation not working as expected in asyncio, no?

Content

> I very doubt if any sane code is organizing like this test: start delayed reading, cancel it and read again.

Hm, cancellation should work correctly no matter how "sane" or "insane" the user code is.

> The worse, neither previous not current sock_read() implementation doesn't prevent the concurrent reading which basically delivers data in an unpredictable order.

But we're not discussing using a socket concurrently -- asyncio explicitly does not support that for the sock_ api. 

AFAICT this issue is about consequent cancel operation not working as expected in asyncio, no?

History
Date	User	Action	Args
2020-02-25 23:38:54	yselivanov	set	recipients: + yselivanov, ned.deily, asvetlov, abacabadabacaba, lukasz.langa
2020-02-25 23:38:54	yselivanov	set	messageid: <1582673934.79.0.418050528066.issue30064@roundup.psfhosted.org>
2020-02-25 23:38:54	yselivanov	link	issue30064 messages
2020-02-25 23:38:53	yselivanov	create