Marc-Andre Lemburg added the comment: On 07.11.2014 11:12, Arfrever Frehtes Taifersar Arahesis wrote: > > Arfrever Frehtes Taifersar Arahesis added the comment: > > _ssl has leading underscore. > Privateness is "inherited", so both A._B.C and A._B._D are private.
No, the use of the underscore in _ssl is per convention that C implementation part of stdlib modules are moved into modules that start with an underscore. This doesn't mean that the APIs in those modules are private, otherwise many C implementations we have in the stdlib would be private :-) Also note that _ssl.sslwrap is special in that it's the main interface between _ssl and ssl. BTW: The sslwrap_simple() API was also removed in 2.7.9. Note: Any libraries that need to monkey patch the Python network stdlib will need access to these APIs. Given that the ssl implementation changed a lot in 2.7.9, I think special care has to be taken not to break too many of these. Using gevent and eventlet as test cases for whether backwards compatibility is good enough sounds like a workable approach, IMO. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22438> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com