#7377: Symbolic Ring to Maxima via EclObject
-----------------------------------------------------------------------+----
Reporter: nbruin |
Owner: nbruin
Type: enhancement |
Status: needs_work
Priority: major |
Milestone: sage-feature
Component: symbolics |
Keywords:
Author: Nils Bruin, Jean-Pierre Flori |
Upstream: N/A
Reviewer: Jean-Pierre Flori, François Bissey, Karl-Dieter Crisman |
Merged:
Work_issues: |
-----------------------------------------------------------------------+----
Comment(by nbruin):
I have tested the new packages with 4.6.2.alpha4 and I am finding largely
agreement with JP. As a baseline, I have used ECL and Maxima from #10766
and #10773 respectively, with applied patches:
{{{
trac_10766-fix_doctest.patch
trac_10766-fix_symbolic_integration_integral.patch
trac_10773-fix_maxima_version.patch
trac_10743-ecl-iter_p1.patch
handlerswap.p2.patch #this is from ticket #10818
}}}
All doctests are OK there. When I further apply
{{{
trac_7377-abstract-maxima_p2.patch
trac_7377-maximalib_p2.patch
trac_7377-fastcalculus_p2.patch
trac_7377-better-ask-error_p2.patch
trac_7377-split_and_refactor.patch
}}}
I am finding doctest failures that are just due to different errors
reporting and floating point, so these can be fixed by changing the
doctests:
{{{
sage -t devel/sage-main/sage/calculus/functional.py # 1 doctests failed
sage -t devel/sage-main/sage/interfaces/maxima.py # 2 doctests failed
sage -t devel/sage-main/sage/symbolic/assumptions.py # 2 doctests failed
sage -t devel/sage-main/sage/symbolic/integration/integral.py # 5
doctests failed
}}}
Furthermore,
{{{
sage -t devel/sage-main/sage/tests/startup.py # 1 doctests failed
}}}
usually fails. Note that we are now initializing ECL upon startup, so
we're really doing more work. Should we be lazy with this? This just means
that the calculus maxima instance would have to be made lazy (i.e., set to
a function that initializes maxima and then rebinds sage.calculus.maxima)
{{{
sage -t devel/sage-main/sage/structure/sage_object.pyx # 1 doctests
failed
}}}
needs a pickling expert
{{{
sage -t devel/sage-main/sage/interfaces/gap3.py # Time out
}}}
this is a real error that was probably introduced by
{{{split_and_refactor}}}. The timeout is caused by an infinite recursion
upon exit (run with -verbose) and probably has to do with the fact that
{{{
sage: gap3("1+2")
}}}
now fails differently. It seems that a "name()" attribute is missing. If
you now try to "quit()", an infinite loop on some Exception resolution is
triggered, but I expect the damage happened in the line above. gap3 is
optional, by the way, but the error apparently already happens with tests
that check the absence of gap3.
Impressive progress indeed!
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7377#comment:78>
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.
