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 tim.peters
Recipients eric.smith, jdemeyer, mark.dickinson, rhettinger, sir-sigurd, tim.peters
Date 2018-10-02.18:32:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A meta-comment:  a great deal of work has been done on non-crypto hashes in recent years.  I'm not interested in rolling our own if one of the "winners" from that process can be adapted.  For that reason, I've only been looking at those that scored 10 (best possible) on Appleby's SMHasher[1] test suite, which is used by everyone who does recognized work in this field.  SeaHash appears to be the fastest of those, with short & simple code.

I'm concerned that I've been putting way too much weight on "the new" tuple test.  That uses a grand total of 10 tiny integers in -5 .. 5 (omits -1).  _All_ base-component variation is in the last 3 bits, while the top 61 bits are all 0 or all 1.  Great for testing nested tuples with tiny mixed-sign integers, but that's a minuscule region of the problem space.

Date User Action Args
2018-10-02 18:32:29tim.peterssetrecipients: + tim.peters, rhettinger, mark.dickinson, eric.smith, jdemeyer, sir-sigurd
2018-10-02 18:32:29tim.peterssetmessageid: <>
2018-10-02 18:32:29tim.peterslinkissue34751 messages
2018-10-02 18:32:29tim.peterscreate