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 zach.ware
Recipients alex, jeremy.kloth, ned.deily, python-dev, steve.dower, zach.ware
Date 2015-04-11.23:20:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1428794412.48.0.434667895543.issue23686@psf.upfronthosting.co.za>
In-reply-to
Content
Looks like that covers it.  The one thing I'm concerned about is that, historically, we've always said "you can point our build system at whatever version of OpenSSL you want and it should work", but obviously this locks us in to 1.0.2+.  Really, there shouldn't be much reason to use anything else, but I'm not sure we want to give up that ability.  I have no idea if anybody actually relies on it though; we could just commit it and backpedal later if anybody complains.
History
Date User Action Args
2015-04-11 23:20:12zach.waresetrecipients: + zach.ware, ned.deily, alex, jeremy.kloth, python-dev, steve.dower
2015-04-11 23:20:12zach.waresetmessageid: <1428794412.48.0.434667895543.issue23686@psf.upfronthosting.co.za>
2015-04-11 23:20:12zach.warelinkissue23686 messages
2015-04-11 23:20:12zach.warecreate