[issue32951] Prohibit direct instantiation of SSLSocket and SSLObject

Change by Christian Heimes : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue32951] Prohibit direct instantiation of SSLSocket and SSLObject

Cheryl Sabella added the comment: Can this issue be closed as resolved? -- nosy: +cheryl.sabella ___ Python tracker ___ ___ Python-

[issue32951] Prohibit direct instantiation of SSLSocket and SSLObject

Christian Heimes added the comment: New changeset 89c2051a554d2053ac87b0adbf11ed0f1bb65db3 by Christian Heimes in branch '3.7': [3.7] bpo-32951: Disable SSLSocket/SSLObject constructor (GH-5864) (#5925) https://github.com/python/cpython/commit/89c2051a554d2053ac87b0adbf11ed0f1bb65db3 ---

[issue32951] Prohibit direct instantiation of SSLSocket and SSLObject

Change by Christian Heimes : -- pull_requests: +5696 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue32951] Prohibit direct instantiation of SSLSocket and SSLObject

Change by Christian Heimes : -- keywords: +patch pull_requests: +5662 stage: needs patch -> patch review ___ Python tracker ___ ___ P

[issue32951] Prohibit direct instantiation of SSLSocket and SSLObject

Christian Heimes added the comment: Antoine Pitrou replied: The ssl.SSLSocket constructor was never meant to be called by user code directly (and I don't think we document it as such). Anyone doing this is asking for trouble (including compatibility breakage as we change the constructor signat

[issue32951] Prohibit direct instantiation of SSLSocket and SSLObject

New submission from Christian Heimes : The constructors of SSLObject and SSLSocket were never documented, tested, or meant to be used directly. Instead users were suppose to use ssl.wrap_socket or an SSLContext object. The ssl.wrap_socket() function and direct instantiation of SSLSocket has mu