Eric V. Smith added the comment: hash() is not defined to be unique, so you're always going to have collisions. The behavior of hash() for int that you're seeing is not a bug.
There's some background here: http://stackoverflow.com/questions/10130454/why-do-1-and-2-both-hash-to-2-in-python ---------- components: +Interpreter Core -Library (Lib) nosy: +eric.smith resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22973> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
