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 habnabit
Recipients Arfrever, asvetlov, bjornedstrom, christian.heimes, englabenny, ezio.melotti, gregory.p.smith, habnabit, jcea, maker, pitrou, python-dev, sbt
Date 2013-06-27.05:56:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As long as the reference Keccak code is going to live in the python stdlib anyway, I would /greatly/ appreciate it if the Keccak sponge function was directly exposed instead of just the fixed parameters used for SHA-3. 

A Keccak sponge can have a much wider range of rates/capacities, and after absorption can have any number of bytes squeezed out. The ability to get an unbounded number of bytes out is very useful and I've written some code that uses that behavior. I ended up having to write my own Keccak python library since none of the other SHA-3 libraries exposed this either.
Date User Action Args
2013-06-27 05:56:59habnabitsetrecipients: + habnabit, gregory.p.smith, jcea, pitrou, christian.heimes, ezio.melotti, Arfrever, asvetlov, englabenny, maker, python-dev, sbt, bjornedstrom
2013-06-27 05:56:59habnabitsetmessageid: <>
2013-06-27 05:56:59habnabitlinkissue16113 messages
2013-06-27 05:56:59habnabitcreate