#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 vbraun):
Float should be treated analogously, but not on this ticket.
`long` is gone in Python 3 so its going to go solve itself eventually.
BTW I don't think that we always have to return Sage ints; E.g. if a
Python int/float is used as a label then I don't really care. But Sage
functions that '''count''' something should return Sage integers as that
number has a combinatorial / number theoretic meaning. Similarly, Sage
functions that perform a machine-precision floating-point computation
should return RDF.
--
Ticket URL: <http://trac.sagemath.org/ticket/19029#comment:14>
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.
