Author njs
Recipients YoSTEALTH, benjamin.peterson, giampaolo.rodola, martin.panter, njs, pitrou, stutzbach, vstinner, xgdomingo
Date 2019-10-10.10:56:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1570704990.48.0.0102633260734.issue32561@roundup.psfhosted.org>
In-reply-to
Content
The proposal is to be able to run io module operations in two modes: the regular one, and one where performing actual I/O is forbidden – so if they go down the stack and can fulfill the operation from some in-memory buffer, great, they do that, and if not, they raise an error.

It turns out that this is actually the right primitive to enable async disk access. That's the only target use case, and there's no IO loop involved. If you wanted to keep async disk access separate from the io module, then what we'd have to do is to create a fork of all the code in the io module, and add this feature to it. Which doesn't seem like a good design :-).
History
Date User Action Args
2019-10-10 10:56:30njssetrecipients: + njs, pitrou, vstinner, giampaolo.rodola, benjamin.peterson, stutzbach, martin.panter, YoSTEALTH, xgdomingo
2019-10-10 10:56:30njssetmessageid: <1570704990.48.0.0102633260734.issue32561@roundup.psfhosted.org>
2019-10-10 10:56:30njslinkissue32561 messages
2019-10-10 10:56:30njscreate