#14748: Deal with DeprecationWarning(s) that appear when using the BoundClass
----------------------------------+-----------------------------------------
       Reporter:  strogdon        |         Owner:  jason           
           Type:  defect          |        Status:  needs_review    
       Priority:  major           |     Milestone:  sage-5.11       
      Component:  misc            |    Resolution:                  
       Keywords:                  |   Work issues:                  
Report Upstream:  N/A             |     Reviewers:  Travis Scrimshaw
        Authors:  Steven Trogdon  |     Merged in:                  
   Dependencies:                  |      Stopgaps:                  
----------------------------------+-----------------------------------------

Comment (by strogdon):

 Thanks Travis. Before I make changes, additionally what is the correct way
 to format the returned expression
 {{{
 ----> 3         functools.partial.__init__(self, f, i, j)
 }}}
 The {{{----> 3}}} only appears when things are entered from the Sage
 prompt. I suspect it is ignored when doctesting. When doctesting a file
 that which is returned is something like
 {{{
 Traceback (most recent call last):
 ...
     functools.partial.__init__(self, f, i, j)
 }}}
 Doctesting seems to be insensitive to either of the above when comparing
 Expected: to Got: as long as there is some whitespace before
 {{{
 functools.partial.__init__(self, f, i, j)
 }}}

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14748#comment:10>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to