Author gregory.p.smith
Recipients Arfrever, BreamoreBoy, asvetlov, bjornedstrom, christian.heimes, dstufft, englabenny, ezio.melotti, gregory.p.smith, haakon, habnabit, haypo, jcea, larry, loewis, markk, pitrou, python-dev, sbt, tim.peters
Date 2014-01-02.20:17:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388693824.6.0.555212852286.issue16113@psf.upfronthosting.co.za>
In-reply-to
Content
I would not bother pulling this out until the week before RC1 if the standard has not yet been declared final.

Otherwise, -1 on keeping it under another name.  The only hashes we bundle should be standard ones as those are the only ones people will want to use in the long run.  We'd be saddled with carrying along a non-standard likely not widely used algorithm implementation forever otherwise.

even if sha3 isn't declared before 3.4rc1, people building 3.4 against a sufficiently modern version of openssl that includes sha3 (as i'm sure some version will) will still have access to the algorithm.

otherwise i'm sure someone will package this as a module on pypi for older pythons regardless.
History
Date User Action Args
2014-01-02 20:17:04gregory.p.smithsetrecipients: + gregory.p.smith, tim.peters, loewis, jcea, pitrou, haypo, larry, christian.heimes, habnabit, ezio.melotti, Arfrever, asvetlov, englabenny, BreamoreBoy, python-dev, sbt, bjornedstrom, dstufft, markk, haakon
2014-01-02 20:17:04gregory.p.smithsetmessageid: <1388693824.6.0.555212852286.issue16113@psf.upfronthosting.co.za>
2014-01-02 20:17:04gregory.p.smithlinkissue16113 messages
2014-01-02 20:17:04gregory.p.smithcreate