Mark Dickinson added the comment: There's nothing wrong with two different Decimal objects having the same hash (indeed, it's inevitable, given that there are fewer than 2**64 hash values available, and many more possible Decimal objects). It only becomes a problem if you have a largish naturally-occurring dataset whose values all end up falling into the same hash bucket, resulting in linear-time dict operations instead of constant time.
I don't think that's the case here: each example of this form only has two different values with the same hash. @Radosław Szalski: is this causing problems in a real application? If not, I think it should be closed as "won't fix". Note that Python 3 is not subject to this issue: it uses a different hashing technique (as described in the issue 8188 that you already linked to). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27265> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
