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 pitrou
Recipients Jeremy.Hylton, brett.cannon, eltoder, eric.araujo, ncoghlan, pitrou, rhettinger
Date 2013-01-16.18:57:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358362647.26.0.443347525413.issue11983@psf.upfronthosting.co.za>
In-reply-to
Content
> It doesn't actually fix the bug and makes hash inconsistent with cmp.

The only constraint is that a == b imply hash(a) == hash(b). But the converse doesn't have to be true, i.e. if it perfectly possible to have hash(a) == hash(b) and a != b (pretty much by definition of a hash function, actually).

What Brett's change means is that the hash function isn't as fine-grained as it could be, but I'm not sure it's very important for code objects.

Of course, that Brett's commit doesn't fix the original bug (if confirmed) is a more annoying issue :-)
History
Date User Action Args
2013-01-16 18:57:27pitrousetrecipients: + pitrou, brett.cannon, rhettinger, ncoghlan, eric.araujo, Jeremy.Hylton, eltoder
2013-01-16 18:57:27pitrousetmessageid: <1358362647.26.0.443347525413.issue11983@psf.upfronthosting.co.za>
2013-01-16 18:57:27pitroulinkissue11983 messages
2013-01-16 18:57:27pitroucreate