➜

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 ncoghlan
Recipients Andrew.Grover, baikie, brian, exarkun, giampaolo.rodola, jackdied, ncoghlan, neologix, pitrou, python-dev, rosslagerwall, synapse, therve, vstinner, wiml
Date 2011-08-23.04:21:34
SpamBayes Score 0.012114908
Marked as misclassified No
Message-id <1314073295.87.0.25437792813.issue6560@psf.upfronthosting.co.za>
In-reply-to
Content 
Attached patch (ssl_fixes_v1) makes the presence of the sendmsg/recvmsg methods in the ssl module conditional on their being present in the underlying socket module.

However, in doing this, I noticed that these methods will, at best, work during the time between connection and the socket going secure and were not added to the list of methods that the SSL is documented as exposing. Perhaps we should just ditch them entirely?
History
Date User Action Args
2011-08-23 04:21:35ncoghlansetrecipients: + ncoghlan, exarkun, pitrou, therve, vstinner, jackdied, baikie, giampaolo.rodola, synapse, Andrew.Grover, wiml, neologix, rosslagerwall, python-dev, brian
2011-08-23 04:21:35ncoghlansetmessageid: <1314073295.87.0.25437792813.issue6560@psf.upfronthosting.co.za>
2011-08-23 04:21:34ncoghlanlinkissue6560 messages
2011-08-23 04:21:34ncoghlancreate