#9224: Unify sage-test and sage-ptest
---------------------------+------------------------------------------------
Reporter: mpatel | Owner: mvngu
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: doctest | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by cwitty):
I do like the idea of merging sage-test and sage-ptest.
Your Doctester API seems reasonable at first glance; there might have to
be minor changes when it's actually implemented, but it's surely basically
sound. (I mean that it has to be possible to split sage-(p)test into
pieces, one of which implements your Doctester API, and one which calls
it.)
Merging sage-doctest into the same code seems trickier, especially if you
mean it to also run in the same process.
I'm afraid I'm not giving very good feedback... "sounds like a good idea,
but it might be hard" :) The problem is that at the moment I don't
understand sage-test, sage-ptest, and sage-doctest well enough to give
more detailed comments.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9224#comment:11>
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.
