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 christian.heimes, giampaolo.rodola, gvanrossum, janssen, pitrou
Date 2013-11-22.13:22:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385126530.2432.1.camel@fsol>
In-reply-to <>
> A few weeks ago I suggested the addition of
> ssl.create_default_context() to the stdlib. The patch implements my
> proposal. It replaces code in several of modules with one central
> function. The patch also removes ssl.wrap_socket() in favor for a
> SSLContext object.

Can you call it create_default_client_context() (a bit long) and/or
stress that it's for client use?

Or will it be ok for server purposes too, i.e. do you promise that it'll
never get CERT_REQUIRED by default?
Date User Action Args
2013-11-22 13:22:13pitrousetrecipients: + pitrou, gvanrossum, janssen, giampaolo.rodola, christian.heimes
2013-11-22 13:22:13pitroulinkissue19689 messages
2013-11-22 13:22:13pitroucreate