#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 jmantysalo):
Should this be closed as wontfix? The basic problem seems to be that we
have no common view of what to do.
(Except that I had made an error where `X.foo()` returned python int `1`
when `X` was a special case and Sage Integer `n` otherwise. It was catch
by ncohen. For this I think we all have same view: output type should be
same in both cases.)
--
Ticket URL: <http://trac.sagemath.org/ticket/19029#comment:21>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
