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 josh.r
Recipients BreamoreBoy, flambda, josh.r, ncoghlan, pitrou, pmoody, tim.peters
Date 2014-06-21.03:24:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403321060.78.0.745647559281.issue20446@psf.upfronthosting.co.za>
In-reply-to
Content
@Tim: Sorry, forgot the internals there (I read all that a while ago, but it's not easy to keep all the details in mind). Apparently there are four reasons this isn't actually a problem. :-)

I agree it's kind of silly that it's converted to a hex string before hashing. Maybe the person writing the code also forgot about sequential hashes being harmless and thought using string hashes (that vary more erratically in modern SIP hash Python) over int hashes would reduce collisions?
History
Date User Action Args
2014-06-21 03:24:20josh.rsetrecipients: + josh.r, tim.peters, ncoghlan, pitrou, pmoody, BreamoreBoy, flambda
2014-06-21 03:24:20josh.rsetmessageid: <1403321060.78.0.745647559281.issue20446@psf.upfronthosting.co.za>
2014-06-21 03:24:20josh.rlinkissue20446 messages
2014-06-21 03:24:20josh.rcreate