Antoine Pitrou added the comment:
The reason is that wrap_socket() is there only for compatibility reasons, and
I'd like people to switch to SSLContext instead. 12-argument functions are only
good for LISPers ;-)
As for SSLSocket, its constructor isn't a public API.
--
resolution: ->
New submission from Vinay Sajip:
The wrap_socket function in ssl.py (unlike the method of the same name in
SSLContext) doesn't accept a server_hostname argument, despite the fact that
it's a one-liner calling SSLSocket, which does take that argument. It it like
this for a reason, or just an ov
