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 lemburg
Recipients alex, dstufft, jeremy.kloth, larry, lemburg, ned.deily, pitrou, python-dev, steve.dower, zach.ware
Date 2015-04-13.23:57:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <552C57E9.7030208@egenix.com>
In-reply-to <1428968498.61.0.914160220191.issue23686@psf.upfronthosting.co.za>
Content
On 14.04.2015 01:41, Donald Stufft wrote:
> 
> I'm pretty massively +1 in Python shipping 1.0.2 (or really, whatever the latest OpenSSL is) wherever it can, including the OSX installers even on systems where Apple ships it's ancient OpenSSL.

Eventually, yes, but the question is: is jumping on such an early
release of a new OpenSSL branch a good idea.
History
Date User Action Args
2015-04-13 23:57:36lemburgsetrecipients: + lemburg, pitrou, larry, ned.deily, alex, jeremy.kloth, python-dev, zach.ware, steve.dower, dstufft
2015-04-13 23:57:34lemburglinkissue23686 messages
2015-04-13 23:57:34lemburgcreate