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 ncoghlan
Recipients alex, christian.heimes, dstufft, giampaolo.rodola, janssen, kushal.das, ncoghlan, ned.deily, pitrou, suki
Date 2015-07-05.10:34:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1436092448.18.0.538382424122.issue23965@psf.upfronthosting.co.za>
In-reply-to
Content
I've attached the patch for my initial attempt at addressing this, but I think my results show I went down completely the wrong path.

Specifically, the three new tests are "failing":

FAIL: test_protocol_sslv23_not_available (test.test_ssl.ThreadedTests)
----------------------------------------------------------------------
AssertionError: Client protocol PROTOCOL_SSLv23 succeeded with server protocol PROTOCOL_SSLv23!

FAIL: test_protocol_sslv2_not_available (test.test_ssl.ThreadedTests)
----------------------------------------------------------------------
AssertionError: Client protocol SSLv2 succeeded with server protocol SSLv2!

FAIL: test_protocol_sslv3_not_available (test.test_ssl.ThreadedTests)
----------------------------------------------------------------------
AssertionError: Client protocol PROTOCOL_SSLv3 succeeded with server protocol PROTOCOL_SSLv3!

So I'm going to revert this attempt entirely, and instead start by introducing some appropriate use of subtests to get more info out of the failing examples.
History
Date User Action Args
2015-07-05 10:34:08ncoghlansetrecipients: + ncoghlan, janssen, pitrou, giampaolo.rodola, christian.heimes, ned.deily, alex, kushal.das, dstufft, suki
2015-07-05 10:34:08ncoghlansetmessageid: <1436092448.18.0.538382424122.issue23965@psf.upfronthosting.co.za>
2015-07-05 10:34:08ncoghlanlinkissue23965 messages
2015-07-05 10:34:07ncoghlancreate