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 pitrou
Recipients asvetlov, giampaolo.rodola, pitrou, vstinner, yselivanov
Date 2017-11-08.13:42:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <6d22f382-164f-4677-5bda-84e4fb2aa324@free.fr>
In-reply-to <1510148421.2.0.213398074469.issue31970@psf.upfronthosting.co.za>
Content
Le 08/11/2017 à 14:40, Giampaolo Rodola' a écrit :
> Exposing sendfile() should be straightforward.

sendfile() is not useful for data that's read from (or written to) memory.

> As for a readinto()-like functionality: the only thing I'm aware of is splice() syscall but it's Linux only.

This is not the abstraction level we are talking about.  The problem is
the Protocol API imposes copies by default (data_received() gives you an
arbitrarily-sized bytes object that doesn't match how your protocol
chunks data).
History
Date User Action Args
2017-11-08 13:42:30pitrousetrecipients: + pitrou, vstinner, giampaolo.rodola, asvetlov, yselivanov
2017-11-08 13:42:29pitroulinkissue31970 messages
2017-11-08 13:42:29pitroucreate