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 ncoghlan
Recipients eric.smith, gpolo, hagen, ncoghlan
Date 2008-12-19.21:24:05
SpamBayes Score 9.5391e-07
Marked as misclassified No
Message-id <1229721847.32.0.351398738273.issue4701@psf.upfronthosting.co.za>
In-reply-to
Content
The origin of the unnecessary hashfunc casts is just me following some
of the more specific examples of filling in the tp_hash slot too closely
without checking if the cast was still needed.

I'll apply and backport Hagen's patches to 3.0 soon (as well as fixing
some other non-hashable types such as slice() to use
PyHash_NotImplemented), but first I want to understand why range()
exhibits this behaviour, while other classes with a superficially
similar implementation (such as bytearray) do not.
History
Date User Action Args
2008-12-19 21:24:07ncoghlansetrecipients: + ncoghlan, eric.smith, gpolo, hagen
2008-12-19 21:24:07ncoghlansetmessageid: <1229721847.32.0.351398738273.issue4701@psf.upfronthosting.co.za>
2008-12-19 21:24:06ncoghlanlinkissue4701 messages
2008-12-19 21:24:05ncoghlancreate