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, janssen, ncoghlan, neologix, pitrou, python-dev, rosslagerwall, synapse, therve, vstinner, wiml
Date 2011-08-23.12:32:44
SpamBayes Score 1.3456537e-05
Marked as misclassified No
Message-id <1314102765.45.0.882984484329.issue6560@psf.upfronthosting.co.za>
In-reply-to
Content
Regarding the 'missing methods' aspect, the SSL docs are already pretty clear that SSLSocket objects don't expose the full socket API:

http://docs.python.org/dev/library/ssl#ssl-sockets

Those docs are actually what really got me started down the path of wondering whether or not these new methods even belong on SSLSocket in the first place.
History
Date User Action Args
2011-08-23 12:32:45ncoghlansetrecipients: + ncoghlan, exarkun, janssen, pitrou, therve, vstinner, jackdied, baikie, giampaolo.rodola, synapse, Andrew.Grover, wiml, neologix, rosslagerwall, python-dev, brian
2011-08-23 12:32:45ncoghlansetmessageid: <1314102765.45.0.882984484329.issue6560@psf.upfronthosting.co.za>
2011-08-23 12:32:44ncoghlanlinkissue6560 messages
2011-08-23 12:32:44ncoghlancreate