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 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 <>
> 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?
Date User Action Args
2020-02-25 23:38:54yselivanovsetrecipients: + yselivanov, ned.deily, asvetlov, abacabadabacaba, lukasz.langa
2020-02-25 23:38:54yselivanovsetmessageid: <>
2020-02-25 23:38:54yselivanovlinkissue30064 messages
2020-02-25 23:38:53yselivanovcreate