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 Ben.Darnell, Ken.Giusti, benjamin.peterson, cbay, giampaolo.rodola, janssen, jcea, pitrou, r.david.murray, vstinner
Date 2013-05-25.10:57:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369479438.38.0.668022017361.issue8240@psf.upfronthosting.co.za>
In-reply-to
Content
> As for partial writes, I'm not sure if it's backwards compatible to
> turn them on by default, but it might be nice if the option were
> exposed. Partial writes may have less benefit in Python than in C
> since we'd have to reallocate and copy a string instead of just moving 
> a pointer.

You can slice a memoryview() to avoid a copy. But I'm not sure of the point of partial writes here: can't you just send slices that are small enough (e.g. 4KB each)?
History
Date User Action Args
2013-05-25 10:57:18pitrousetrecipients: + pitrou, jcea, janssen, vstinner, giampaolo.rodola, benjamin.peterson, r.david.murray, cbay, Ben.Darnell, Ken.Giusti
2013-05-25 10:57:18pitrousetmessageid: <1369479438.38.0.668022017361.issue8240@psf.upfronthosting.co.za>
2013-05-25 10:57:18pitroulinkissue8240 messages
2013-05-25 10:57:18pitroucreate