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 Lukasa, alex, christian.heimes, dstufft, giampaolo.rodola, janssen, martin.panter, ncoghlan, orsenthil, python-dev, vstinner
Date 2016-09-11.07:43:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473579821.8.0.516244404663.issue28022@psf.upfronthosting.co.za>
In-reply-to
Content
Leaving the option of context caching entirely to the caller would definitely make things simpler - my main interest is just in avoiding a hard compatibility break for folks that aren't doing anything particularly wrong, by which I mean specifically cases where a wrap_socket() implementation like this one would continue to work for them:

    def wrap_socket(sock, *args, *kwds):
        return ssl.get_default_context().wrap_socket(sock, *args, **kwds)
History
Date User Action Args
2016-09-11 07:43:41ncoghlansetrecipients: + ncoghlan, janssen, orsenthil, vstinner, giampaolo.rodola, christian.heimes, alex, python-dev, martin.panter, dstufft, Lukasa
2016-09-11 07:43:41ncoghlansetmessageid: <1473579821.8.0.516244404663.issue28022@psf.upfronthosting.co.za>
2016-09-11 07:43:41ncoghlanlinkissue28022 messages
2016-09-11 07:43:41ncoghlancreate