#9590: Doctest failures in cone.py and toric_lattice_element.pyx on 32-bit Linux
----------------------------------+-----------------------------------------
   Reporter:  mpatel              |       Owner:  mhampton       
       Type:  defect              |      Status:  positive_review
   Priority:  blocker             |   Milestone:  sage-4.5.2     
  Component:  geometry            |    Keywords:                 
     Author:  Andrey Novoseltsev  |    Upstream:  N/A            
   Reviewer:  Leif Leonhardy      |      Merged:                 
Work_issues:                      |  
----------------------------------+-----------------------------------------

Comment(by ddrake):

 I thought that maybe Leif's suggestions would be preferred, but Carl Witty
 said (https://groups.google.com/group/sage-
 devel/browse_thread/thread/9a0f357c8ec9bbd):
 {{{
 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
 3) define your hash function to produce a 32-bit output that's the
 same on 32-bit and 64-bit systems; doctest an instance of that output
 4) doctest hash value equality without ever showing a doctest output

 plus one instance where the hash output is marked "# random".

 So whatever you do with this particular patch, it won't make things
 much worse :)
 }}}
 So, I'll merge this, and maybe we'll figure out a better way to test
 hashing later.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9590#comment:9>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to