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 larry
Recipients Jim.Jewett, Lukasa, alex, christian.heimes, dstufft, georg.brandl, giampaolo.rodola, hynek, janssen, larry, python-dev, steve.dower
Date 2016-09-07.22:10:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473286249.12.0.954166951095.issue27850@psf.upfronthosting.co.za>
In-reply-to
Content
Okay.  We (Ned Deily + Steve Dower + me) talked it over here at the core dev sprints, and they convinced me that it's basically okay to add the CHACHA20 string to 3.4 and 3.5--it has some history, and OpenSSL is a little different, etc etc.  So go for it.

I suspect it won't affect very many people anyway, because not many will use Python 3.4 with a version of OpenSSL that supports ChaCha20.  It's more likely with 3.5 users--not with our binary installers, but perhaps the Linux distributions that release during what remains of 2016.
History
Date User Action Args
2016-09-07 22:10:49larrysetrecipients: + larry, georg.brandl, janssen, giampaolo.rodola, christian.heimes, alex, python-dev, hynek, Jim.Jewett, steve.dower, dstufft, Lukasa
2016-09-07 22:10:49larrysetmessageid: <1473286249.12.0.954166951095.issue27850@psf.upfronthosting.co.za>
2016-09-07 22:10:49larrylinkissue27850 messages
2016-09-07 22:10:49larrycreate