[Python-Dev] [PEP466] SSLSockets, and sockets, _socketobjects oh my! (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Thu Jul 24 00:06:26 CEST 2014
- Previous message: [Python-Dev] [PEP466] SSLSockets, and sockets, _socketobjects oh my!
- Next message: [Python-Dev] Does Zip Importer have to be Special?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 24 Jul 2014 05:37, "Alex Gaynor" <alex.gaynor at gmail.com> wrote:
Possible solutions are: * Pass the SSLObject in addition to the socket.socket object to the C code. This generates some additional divergence from the Python3 code, but is probably basically straightforward. * Try to refactor the socket code in the same way as Python3 did, so we can pass only the SSLObject here. This is some nasty scope creep for PEP466, but would make the overall ssl.c diff smaller. * Some super sweet and simple thing I haven't thought of yet. Thoughts?
Wearing my "risk management" hat, option 1 sounds significantly more appealing than option 2 :)
Cheers, Nick. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140724/0fa04c0d/attachment.html>
- Previous message: [Python-Dev] [PEP466] SSLSockets, and sockets, _socketobjects oh my!
- Next message: [Python-Dev] Does Zip Importer have to be Special?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]