#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):
doctesting on 4.6.1 yields failures in only 12 files, and most of these
are just changed formatting of output, numerical noise because floats are
now binarily copied rather than transcribed via decimal string
representations, and because some errors get reported differently. (For
ECL everything is a RuntimeError, for instance).
List here:
* {{{devel/sage/sage/symbolic/assumptions.py}}}: "Assumption
is inconsistent" errors get reported differently
* {{{devel/sage/sage/symbolic/function_factory.py}}}: Serious issues with
translating FDerivative constructs (it doesn't work at the moment)
* {{{devel/sage/sage/symbolic/expression.pyx}}}: A strange
issue with {{{(x*log(9)).simplify_log('all')}}}. Oddly,
{{{(x*log(3/7)).simplify_log('all')}}} does behave correctly.
* {{{devel/sage/sage/symbolic/integration/integral.py}}}:
"Maxima asks a question" errors get reported differently, float issues
* {{{devel/sage/sage/interfaces/maxima.py}}}: "Maxima asks
a question" errors get reported differently. These doctests are wrong,
because
they test the maxima_lib interface via calculus, not a real maxima
interface.
* {{{devel/sage/sage/interfaces/maxima_abstract.py}}}:
These doctests were never adapted
* {{{devel/sage/sage/calculus/calculus.py}}}: Whitespace
and nintegral reports failure differently.
* {{{devel/sage/sage/calculus/wester.py}}}: Looks like
correct answer, but differently collected.
* {{{devel/sage/sage/calculus/tests.py}}}: Odd errors. They seem to depend
on
context. Perhaps assumptions that aren't properly forgotten or max_to_sr
cache
that gets spoilt?
* {{{devel/sage/sage/calculus/desolvers.py}}}: lots of
problems. The desolve interface probably needs treatment like the
to_poly_solve
routine.
* {{{devel/sage/sage/calculus/functional.py}}}: "Maxima
asks a question" gets reported differently
* {{{devel/sage/sage/symbolic/assumptions.py}}}:
Inconsistent assumptions get reported differently.
Most of these are a matter of changing the doctests to the generated
answer, but
a few serious issues remain.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7377#comment:46>
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.
