On Mon, Mar 31, 2008 at 11:08 AM, Timothy G Abbott <[EMAIL PROTECTED]> wrote:
> Okay, I've created a patch to do this.
>
> However, it results in a number of doctest failures. They fall into two
> classes:
>
> 1) a bunch of errors, mostly in tut.py and the plotting code, that try to
> write to the working directory from code like "a.save('a')".
>
> 2) Places where the doctests only work if run from the same directory as
> the module they're testing, i.e. when they do "import
> matrix_integer_dense_hnf" rather than "import
> sage.matrix.matrix_integer_dense_hnf as matrix_integer_dense_hnf" or
> similar.
>
> There are a lot of type (1) errors, and I think it's nice for the examples
> to be able to write files to the current working directory rather than
> somewhere else, so this rules out changing the doctests. This might be
> best handled by having sage-maketest chdir to $SAGE_TESTDIR before running
> the tests. Doctests for that are currently running.
>
> I think the type (2) errors are bugs in the doctests (it's certainly a bad
> documentation example if it only works from that directory), and once my
> current doctest run finishes I'll submit patches for them.
I strongly agree with you on this point.
-- William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
