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 rhettinger
Recipients Arfrever, asvetlov, bjornedstrom, christian.heimes, dstufft, ezio.melotti, gregory.p.smith, haakon, habnabit, jcea, larry, loewis, markk, pitrou, python-dev, rhettinger, sbt, spatz, tim.peters, vstinner
Date 2016-08-22.02:18:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The SHAKEs were low hanging fruits to implement, so I included them.

I don't think this is sufficient motivation.  Each new API is a permanent maintenance and documentation burden.  It is also a burden to every new user seeing the module and trying to decide which offering to use.  We should provide tools that we know people need and error on the side of economy.  I asked a room full of network engineers about SHAKE and not a single one of them had heard of it, so I think it would be premature to add to the standard library.
Date User Action Args
2016-08-22 02:18:07rhettingersetrecipients: + rhettinger, tim.peters, loewis, gregory.p.smith, jcea, pitrou, vstinner, larry, christian.heimes, habnabit, ezio.melotti, spatz, Arfrever, asvetlov, python-dev, sbt, bjornedstrom, dstufft, markk, haakon
2016-08-22 02:18:06rhettingersetmessageid: <>
2016-08-22 02:18:06rhettingerlinkissue16113 messages
2016-08-22 02:18:06rhettingercreate