On Sun, Jul 25, 2010 at 8:11 PM, Dan Drake wrote:
> On Sun, 25 Jul 2010 at 07:11PM -0700, Carl Witty wrote:
>> Hmm... looks like the current state of affairs is a mess. Looking
>> through the 'def __hash__' grep hits in sage/rings, there are quite a
>> few of each of the following:
>>
>> 1) no do
On Sun, 25 Jul 2010 at 07:11PM -0700, Carl Witty wrote:
> Hmm... looks like the current state of affairs is a mess. Looking
> through the 'def __hash__' grep hits in sage/rings, there are quite a
> few of each of the following:
>
> 1) no doctest at all
> 2) provide both 32-bit and 64-bit doctests
On Sun, Jul 25, 2010 at 6:33 PM, Dan Drake wrote:
> Hello,
>
> Ticket #9590 fixes a problem with hashing; it looks like the hash value
> in the doctest is 32- or 64-bit specific, and of course it fails on
> systems that don't match. The solution there is to change a doctest like
>
> sage: h
Hello,
Ticket #9590 fixes a problem with hashing; it looks like the hash value
in the doctest is 32- or 64-bit specific, and of course it fails on
systems that don't match. The solution there is to change a doctest like
sage: hash(foo)
574575757575
into
sage: hash(foo) =
