➜

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 Michael.Gubser, pitrou
Date 2014-01-29.00:40:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390956022.09.0.612106405492.issue20419@psf.upfronthosting.co.za>
In-reply-to
Content 
ssl.wrap_socket is pretty much a legacy API. It has too many parameters already, and I don't really want to make it worse. The SSLContext API is designed to be more palatable, even though it's a bit less compact.

(also, ssl.wrap_socket will implicitly create a new context each time, which is wasteful - especially when context initialization implies loading certificates, etc.)
History
Date User Action Args
2014-01-29 00:40:22pitrousetrecipients: + pitrou, Michael.Gubser
2014-01-29 00:40:22pitrousetmessageid: <1390956022.09.0.612106405492.issue20419@psf.upfronthosting.co.za>
2014-01-29 00:40:22pitroulinkissue20419 messages
2014-01-29 00:40:21pitroucreate