#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):
> On the other hand, it's in solve. Those answers aren't trustworthy if
there's no error either.
In this particular case, I guess we noticed that
{{{
cot: argument 0 isn't in the domain of cot.
}}}
which is true, and so solve should give the empty solution. Would it be
fairly easy to change that solve code to catch this type of wording
`argument 0 isn't in the domain` in which case presumably no solution
''is'' correct? Though...
{{{
(%i6) solve(x*acot(x),x);
cot: argument 0 isn't in the domain of cot.
(%i7) acot(0)
;
%pi
(%o7) ---
2
}}}
which is not ideal. I opened https://sourceforge.net/p/maxima/bugs/2844/
for this.
Anyway, one way or another that doctest failure needs to be dealt with,
and so much the better if it improves the solve code.
--
Ticket URL: <http://trac.sagemath.org/ticket/14308#comment:14>
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.
