#11895: padic_ZZ_pX_CR_element is unhashable
--------------------------------+-------------------------------------------
       Reporter:  mmasdeu       |         Owner:  roed                          
         
           Type:  defect        |        Status:  needs_work                    
         
       Priority:  critical      |     Milestone:  sage-5.4                      
         
      Component:  padics        |    Resolution:                                
         
       Keywords:  p-adic, hash  |   Work issues:  whitespace, line wrapping in 
docstrings
Report Upstream:  N/A           |     Reviewers:  David Loeffler                
         
        Authors:  David Roe     |     Merged in:                                
         
   Dependencies:                |      Stopgaps:                                
         
--------------------------------+-------------------------------------------

Comment (by roed):

 Nils, I agree that there are some horrible compromises to be had on this
 issue.  I would like to make p-adic elements unhashable, but there are
 some nasty consequences of doing so.  We can't add points on elliptic
 curves over p-adic fields.  We can't print matrices.  Out of curiousity I
 tried changing the hash methods on elements of Zp and Qp to raise a
 `TypeError`.  Hundreds of doctest failures.  There's an assumption that
 elements are hashable throughout Sage.

 I don't know what the answer is.  If we can come to a consensus on this
 I'm happy to fix the whitespace issues.  :-)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11895#comment:7>
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