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 Dubslow, christian.heimes, dstufft, larry, ncoghlan, ned.deily, piotr.dobrogost, python-dev, tim.peters
Date 2014-02-14.23:22:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392420143.98.0.138371310897.issue19744@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks Ned - I fixed that test to only run if SSL/TLS is available, and added a new one to test that the command "succeeds" (with a warning printed to stderr) if SSL/TLS is missing.

Larry - over to you to decide whether or not to cherry pick this into the release clone. The remaining misbehaviour that was fixed in the last patch only affects custom source builds, so the beneficiaries would be people trying to build from the source tarball or release tag without SSL/TLS support.
History
Date User Action Args
2014-02-14 23:22:24ncoghlansetrecipients: + ncoghlan, tim.peters, larry, christian.heimes, ned.deily, python-dev, piotr.dobrogost, Dubslow, dstufft
2014-02-14 23:22:23ncoghlansetmessageid: <1392420143.98.0.138371310897.issue19744@psf.upfronthosting.co.za>
2014-02-14 23:22:23ncoghlanlinkissue19744 messages
2014-02-14 23:22:23ncoghlancreate