Showing content from http://mail.python.org/pipermail/python-dev/attachments/20140724/0fa04c0d/attachment.html below:
<p dir="ltr"><br>
On 24 Jul 2014 05:37, "Alex Gaynor" <<a href="mailto:alex.gaynor@gmail.com">alex.gaynor@gmail.com</a>> wrote:<br>
><br>
> Possible solutions are:<br>
><br>
> * Pass the SSLObject *in addition* to the _socket.socket object to the C code.<br>
> Â This generates some additional divergence from the Python3 code, but is<br>
> Â probably basically straightforward.<br>
> * Try to refactor the socket code in the same way as Python3 did, so we can<br>
> Â pass *only* the SSLObject here. This is some nasty scope creep for PEP466,<br>
> Â but would make the overall _ssl.c diff smaller.<br>
> * Some super sweet and simple thing I haven't thought of yet.<br>
><br>
> Thoughts?</p>
<p dir="ltr">Wearing my "risk management" hat, option 1 sounds significantly more appealing than option 2 :)</p>
<p dir="ltr">Cheers,<br>
Nick.<br>
</p>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4