➜

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 jcea
Recipients Arfrever, BreamoreBoy, asvetlov, bjornedstrom, christian.heimes, dstufft, englabenny, ezio.melotti, gregory.p.smith, haakon, habnabit, jcea, larry, loewis, markk, pitrou, python-dev, sbt, tim.peters, vstinner
Date 2015-10-15.00:56:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444870620.17.0.659315138441.issue16113@psf.upfronthosting.co.za>
In-reply-to
Content 
SHA-3 is released.

http://www.nist.gov/manuscript-publication-search.cfm?pub_id=919061

Should we add it to Python 2.7.11, 3.4.4, 3.5.1 or just for 18 months away Python 3.6?. Since this is a security sensitive issue, I would vote for adding it to the maintained releases.
History
Date User Action Args
2015-10-15 00:57:00jceasetrecipients: + jcea, tim.peters, loewis, gregory.p.smith, pitrou, vstinner, larry, christian.heimes, habnabit, ezio.melotti, Arfrever, asvetlov, englabenny, BreamoreBoy, python-dev, sbt, bjornedstrom, dstufft, markk, haakon
2015-10-15 00:57:00jceasetmessageid: <1444870620.17.0.659315138441.issue16113@psf.upfronthosting.co.za>
2015-10-15 00:57:00jcealinkissue16113 messages
2015-10-15 00:56:59jceacreate