#12415: Update doctesting framework
-------------------------------------------------------------------------------------------------------------------------+
       Reporter:  robertwb                                                      
                                         |         Owner:  mvngu         
           Type:  enhancement                                                   
                                         |        Status:  needs_review  
       Priority:  major                                                         
                                         |     Milestone:  sage-5.1      
      Component:  doctest                                                       
                                         |    Resolution:                
       Keywords:                                                                
                                         |   Work issues:                
Report Upstream:  N/A                                                           
                                         |     Reviewers:  Jeroen Demeyer
        Authors:  David Roe, Robert Bradshaw                                    
                                         |     Merged in:                
   Dependencies:  #13147,#13146, #13145, #12723, #12392, #12393, #12395, 
#12396, #12397, #12381, #12382, #12383, #12384  |      Stopgaps:                
-------------------------------------------------------------------------------------------------------------------------+

Comment (by roed):

 Replying to [comment:73 jdemeyer]:
 > Replying to [comment:71 roed]:
 > > Replying to [comment:63 jdemeyer]:
 > > > The doctesting framework seems to hang on
 > > > {{{
 > > > jdemeyer@sage:/release/merger/sage-5.1.beta5-12415$ ./sage -t
 /home/jdemeyer/doctest/sigdie.py
 > > > Running doctests with ID 2012-06-26-14-12-55-fbefc7c4.
 > > > Doctesting 1 file.
 > > > }}}
 > >
 > > Is this behavior acceptable?
 > Not really.  One should get a message that Sage crashed (compare with
 the old doctesting framework).
 Okay, I will look into it.  I assume that the underlying process has
 terminated and I should be able to get at the exit code somehow.

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