#19029: doctest Python vs Sage ints
-------------------------------------+-------------------------------------
       Reporter:  vbraun             |        Owner:
           Type:  enhancement        |       Status:  new
       Priority:  major              |    Milestone:  sage-6.9
      Component:  user interface     |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Volker Braun       |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/vbraun/doctest_python_vs_sage_ints|  
129259d7e537f92b1e55fbb414477231117456fc
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by dkrenn):

 Replying to [comment:16 jmantysalo]:
 > Replying to [comment:15 nbruin]:
 > > I think this makes is rather hard to formulate a clear rule for when
 an `Integer` should really be returned.
 >
 > So should this ticket be closed as wontfix? And maybe add something to
 developer manual.

 To avoid that this ends in nothing. What about
 - adding an something like --show-pyint / --show-pyfloat as an option for
 doctesting (not enabled by default) and maybe
 - adding to the developer guide "you are encouraged to return Sage
 integers (instead of Python integers) unless ..... . The option --show-
 pyint might be useful."

--
Ticket URL: <http://trac.sagemath.org/ticket/19029#comment:17>
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/d/optout.

Reply via email to