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 hodgestar
Recipients giampaolo.rodola, hodgestar, janssen
Date 2008-09-05.12:00:24
SpamBayes Score 6.2333042e-06
Marked as misclassified No
Message-id <1220616027.23.0.108590492195.issue3162@psf.upfronthosting.co.za>
In-reply-to
Content
I've attached a patch for trunk / 2.6 that adds recv_into and
recvfrom_into methods to ssl.SSLSocket and does a minor re-ordering of
the nasty lambdas in __init__. The recv_into method is a port of the one
from 3.0. The recvfrom_into method is a simple "fail if we have an SSL
object or pass down if we don't".

For the record, I'm against the lambdas in SSLSocket.__init__ and would
prefer the solution I suggested previously of putting a hasattr(...)
check into socket.socket (I can submit a patch if useful).

As is probably abundantly clear at the moment :), none of the SSLSocket
methods in questions have tests in test_ssl -- I will move on to trying
to add them next.

I'm also going to attach a patch for 3.0 which adds recvfrom_into (a
port of the 2.6 one).
History
Date User Action Args
2008-09-05 12:00:27hodgestarsetrecipients: + hodgestar, janssen, giampaolo.rodola
2008-09-05 12:00:27hodgestarsetmessageid: <1220616027.23.0.108590492195.issue3162@psf.upfronthosting.co.za>
2008-09-05 12:00:25hodgestarlinkissue3162 messages
2008-09-05 12:00:25hodgestarcreate