#8800: Doctest coverage of categories - numerous coercion fixes
--------------------------+-------------------------------------------------
   Reporter:  SimonKing   |       Owner:  Simon King         
       Type:  defect      |      Status:  needs_work         
   Priority:  major       |   Milestone:  sage-4.6.1         
  Component:  categories  |    Keywords:  categories doctests
     Author:  Simon King  |    Upstream:  N/A                
   Reviewer:              |      Merged:                     
Work_issues:              |  
--------------------------+-------------------------------------------------

Comment(by SimonKing):

 Hi John,

 Replying to [comment:53 cremona]:
 > I just tested on a different 32-bit machine on which I have just built
 4.6.1.alpha3 (and all tests passed):  Same failure as before for
 sage/groups/perm_gps/permgroup.py, and for
 sage/groups/perm_gps/permgroup.py
 >
 > The second one of these is the more worrying in that it goes into an
 infinite recursion.

 I wonder if the recursion comes from the testing framework. Once, I
 observed such recursion in a test, but I could not reproduce it in  an
 interactive session. In addition, I got a return value different from the
 expected - and when I changed the expected  value in the test, the
 recursion disappeared as well.

 Could you change the expected 32-bit value in the test of selmer_group to
 the value that you get in an interactive session, and then try `sage -t
 "sage/rings/number_field/number_field.py"` again?

 Cheers,

 Simon

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