This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Maximilian Blochberger
Recipients Maximilian Blochberger, christian.heimes
Date 2017-02-02.13:37:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486042667.59.0.883968067297.issue29394@psf.upfronthosting.co.za>
In-reply-to
Content
Okay, I see, thanks for the hint. That worked perfectly – I found `asyncio.sslproto._SSLPipe` very useful for that purpose.

I personally consider the behaviour of `ssl.SSLContext.wrap_socket()` unexpected and would raise an exception if that method call is tried on an instance of `ssl.SSLSocket`. But as this would be a change that could lead to backwards compatibility issues (if developers depend on that behaviour) this is probably not a good idea.

I think that the documentation for `ssl.SSLContext.wrap_socket()` has this behaviour to avoid future confusion – including a hint to make use of `ssl.SSLContext.wrap_bio()` instead.
History
Date User Action Args
2017-02-02 13:37:47Maximilian Blochbergersetrecipients: + Maximilian Blochberger, christian.heimes
2017-02-02 13:37:47Maximilian Blochbergersetmessageid: <1486042667.59.0.883968067297.issue29394@psf.upfronthosting.co.za>
2017-02-02 13:37:47Maximilian Blochbergerlinkissue29394 messages
2017-02-02 13:37:47Maximilian Blochbergercreate