#8791: improve doctest coverage of libs/mpmath/ext_main.pyx
-----------------------------+----------------------------------------------
Reporter: mvngu | Owner: mvngu
Type: enhancement | Status: new
Priority: major | Milestone: sage-4.4.1
Component: documentation | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by fredrik.johansson):
Argh. Who wrote this code?
The actual code coverage, indirectly through mpmath's unit tests (which
however aren't run automatically by Sage) is close to 99%, but writing
Sage doctests slipped my mind entirely.
Some of these functions have doctests, but they're added at runtime when
importing mpmath. I'm considering whether statically duplicating them is a
good idea, or whether it's better to just add static placeholders.
Most of these are probably trivial to write, e.g.:
{{{
sage: import mpmath
sage: mpmath.mpf(1).__add__(1)
mpf('2.0')
}}}
But I can't say when I'll have time to do this.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8791#comment:1>
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.
