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.02:44:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I asked in more detail about this on the list, but my main question is why can't wrap_socket() be fixed by doing a rip-and-replace on its internals (e.g. by using a model similar to the one in random, where there's an implicit global Random instance that gets invoked if you use the module level API instead of creating your own instance), rather than having to tell users to change *their* code.

Like Random, I'd like to see SSLContext as a lower level implementation detail that's there for when people need it, but can be largely ignored if they just want the default behaviours (i.e. system trust store with python-dev specified SSL/TLS settings)
Date User Action Args
2016-09-11 02:44:02ncoghlansetrecipients: + ncoghlan, janssen, orsenthil, vstinner, giampaolo.rodola, christian.heimes, alex, python-dev, martin.panter, dstufft, Lukasa
2016-09-11 02:44:02ncoghlansetmessageid: <>
2016-09-11 02:44:02ncoghlanlinkissue28022 messages
2016-09-11 02:44:01ncoghlancreate