#14308: unwanted maxima verbose output
-------------------------------------+-------------------------------------
Reporter: zimmerma | Owner: was
Type: defect | Status: needs_review
Priority: minor | Milestone: sage-6.4
Component: interfaces | Resolution:
Keywords: | Merged in:
Authors: Nils Bruin | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/nbruin/maxima_verbose_output | 972427193788bc3f0c61951b063780772d55edfe
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
> > that error finally make me find the better routine in maxima to
execute maxima code [...]
>
> great!
Indeed! Took me a while to figure out what was going on there but I agree
this is probably better than printing the backtrace (though see
[http://comments.gmane.org/gmane.comp.mathematics.maxima.general/40253
here] for some other discussion; we could have just commented that out in
a patch). The only downside is that it now talks only about ECL and not
Maxima, which may be confusing for some folks. What do you think?
Otherwise this is fine, modulo doctests...
{{{
sage -t src/sage/symbolic/expression.pyx
**********************************************************************
File "src/sage/symbolic/expression.pyx", line 9388, in
sage.symbolic.expression.Expression.solve
Failed example:
solve(acot(x),x)
TypeError: ECL says: cot: argument 0 isn't in the domain of cot.
**********************************************************************
File "src/sage/symbolic/expression.pyx", line 9393, in
sage.symbolic.expression.Expression.solve
Failed example:
solve(acot(x),x,to_poly_solve=True)
TypeError: ECL says: cot: argument 0 isn't in the domain of cot.
**********************************************************************
1 item had failures:
}}}
This comes from
{{{
TESTS:
:trac:`7325` (solving inequalities)::
sage: (x^2>1).solve(x)
[[x < -1], [x > 1]]
Catch error message from Maxima::
sage: solve(acot(x),x)
[]
::
sage: solve(acot(x),x,to_poly_solve=True)
[]
}}}
Amazingly, I personally am responsible for the
[http://trac.sagemath.org/attachment/ticket/7745/trac_7745-upgrade-
maxima.patch code] that catches this. Now that we have the lib etc.,
what do you think? I think it's still okay that we catch an error in
solve and just return that we can't do it, but in retrospect the way I did
it was just enough to get by.
--
Ticket URL: <http://trac.sagemath.org/ticket/14308#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
