#20182: Automatic doctest for external softwares
-------------------------+-------------------------------------------------
Reporter: klee | Owner:
Type: | Status: new
enhancement | Milestone: sage-7.1
Priority: major | Resolution:
Component: | Merged in:
doctest framework | Reviewers:
Keywords: | Work issues:
Authors: | Commit:
Kwankyu Lee | 86a7e6f8cb3845aa4551422941ee081cfc46f713
Report Upstream: N/A | Stopgaps:
Branch: |
public/20182 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by klee):
> I don't know how to balance the laziness with what I'm looking for.
Maybe a summary at the ''end'' of doctesting of which external packages
were detected, or (even better) the intersection of those external
packages which were detected and those for which a test was run.
Because of the lazyset mechanism, at least one test was run for an
external software detected in most cases. There may be exceptional cases
to this, but is this important? By the way, I prefer "external software"
than "external package". Internet is rather a software than a package :-)
> I think it is important to provide feedback about this in order to debug
failed tests (or slow tests, etc.).
I agree. Perhaps we can list the detected softwares at the end of
doctesting as you suggested.
--
Ticket URL: <http://trac.sagemath.org/ticket/20182#comment:35>
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.
