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 Ben.Darnell
Recipients Ben.Darnell, Ken.Giusti, benjamin.peterson, cbay, giampaolo.rodola, janssen, jcea, pitrou, r.david.murray, vstinner
Date 2013-05-22.03:32:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369193531.91.0.863827488033.issue8240@psf.upfronthosting.co.za>
In-reply-to
Content
I vote for enabling SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER by default.  It can catch mistakes (i.e. failure to check the return value of send) in Python just as easily as in C, but I don't think those mistakes are common enough to be worth the headache of this error.  The false positive rate of this error is higher in Python than in C because we don't have direct control over memory and pointers.

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.
History
Date User Action Args
2013-05-22 03:32:12Ben.Darnellsetrecipients: + Ben.Darnell, jcea, janssen, pitrou, vstinner, giampaolo.rodola, benjamin.peterson, r.david.murray, cbay, Ken.Giusti
2013-05-22 03:32:11Ben.Darnellsetmessageid: <1369193531.91.0.863827488033.issue8240@psf.upfronthosting.co.za>
2013-05-22 03:32:11Ben.Darnelllinkissue8240 messages
2013-05-22 03:32:10Ben.Darnellcreate