Author eric.smith
Recipients eric.smith, jdemeyer, mark.dickinson, ned.deily, rhettinger, tim.peters
Date 2018-09-21.10:17:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537525045.11.0.956365154283.issue34751@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with Raymond and Tim here: while it's inevitably true that there are many possible hash collisions, we'd need to see where the current algorithm caused real problems in real code. Pointing out a few examples where there was a collision isn't very helpful.

So, jdemeyer, if it's possible to show (or describe) to us an example of a problem you had, such that we could repeat it, that would be helpful (and necessary) to evaluate any proposed changes.  What were the inputs to hash() that caused a problem, and how did that problem manifest itself?
History
Date User Action Args
2018-09-21 10:17:25eric.smithsetrecipients: + eric.smith, tim.peters, rhettinger, mark.dickinson, ned.deily, jdemeyer
2018-09-21 10:17:25eric.smithsetmessageid: <1537525045.11.0.956365154283.issue34751@psf.upfronthosting.co.za>
2018-09-21 10:17:25eric.smithlinkissue34751 messages
2018-09-21 10:17:25eric.smithcreate