On Jan 23, 12:26 am, slabbe <sla...@gmail.com> wrote:
> Hi Emil,
>
> Well, here is how I interpret it. You tested the file sage/misc/
> citation.pyx and one of the examples inside of that file failed.
> Comparing what was expected and what you got, I think that there no
> whitespace error : the results are really different.
>
> Maybe the term "whitespace error" leads to misinterpretation and could
> be improved. Personally, I though "whitespace errors" was for when the
> only difference between the expected result and the obtained result
> are whitespaces at the end of the line. But, I think I never obtained
> any failed doctest because of whitespace errors. Do anybody ever got
> real whitespaces error? So maybe the sentence could be :
>
> "If the expected result and the one that is got of a failed doctest
> look the same, it might be because of whitespace error: see the file /
> root/.sage//tmp/.doctest_citation.py "
>
> Cheers,
>
> Sébastien Labbé
The exactly same example is given in the code:
def get_systems(cmd):
"""
Returns a list of the systems used in running the command
cmd. Note that the results can sometimes include systems
that did not actually contribute to the computation. Due
to caching and the inability to follow all C calls, it
could miss some dependencies as well.
INPUT:
- ``cmd`` - a string to run
EXAMPLES::
sage: from sage.misc.citation import get_systems
sage: s = get_systems('integrate(x^2, x)'); #priming coercion
model
sage: get_systems('integrate(x^2, x)')
['ginac', 'Maxima']
sage: R.<x,y,z> = QQ[]
sage: I = R.ideal(x^2+y^2, z^2+y)
sage: get_systems('I.primary_decomposition()')
['Singular']
"""
import cProfile, pstats, re
....
I was refering to this comment in the source code
(although I don't exactly understand what it means)
Due
to caching and the inability to follow all C calls, it
could miss some dependencies as well.
...
So I guess there were problems before with this routine. I can run the
maxima command from the commandline, but somehow it is missed in the
test procedere.
The strange thing is, that I use this build to integrate it in a Live
CD build, so I compile, copy the whole sage-directory to integrate it
with the base OS, then make a squashed filesystem. During all this
steps sage stays fully functional, without this error. Finally in the
last step, when I boot up the Live CD build and start sage from this
fresh install, this test fails.
The only thing which changes is the length of SAGE_ROOT . (As far as I
can see)
I am not good enough with python to understand fully what happens in
that test procedere atm, but it seems, the list of built in packages
are tested against a set of commands to look which packages give
correct results.
Either I just accept it that this particulare test fails, or else I
have to do some debugging I guess.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
