➜

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 vstinner
Recipients abarry, alex, christian.heimes, dstufft, giampaolo.rodola, janssen, nemunaire, pitrou, vstinner
Date 2016-07-27.14:25:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469629517.16.0.957097167549.issue27629@psf.upfronthosting.co.za>
In-reply-to
Content 
The change introducing the != SOCK_STREAM check (change a00842b783cf) was made in 2013. It looks like the case was not tested since at least 3 years...

> This will need a test in Lib/test/test_ssl.py to check for this particular case.

Yes, this new test is mandatory to make sure that the feature is not broken again (check for regression).

The workaround is to pass an existing socket...
History
Date User Action Args
2016-07-27 14:25:17vstinnersetrecipients: + vstinner, janssen, pitrou, giampaolo.rodola, christian.heimes, alex, dstufft, abarry, nemunaire
2016-07-27 14:25:17vstinnersetmessageid: <1469629517.16.0.957097167549.issue27629@psf.upfronthosting.co.za>
2016-07-27 14:25:17vstinnerlinkissue27629 messages
2016-07-27 14:25:17vstinnercreate