#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: Maxima question doctests, 100% coverage, Maxima command list
doctest |
------------------------------------------------------------------------------------+
Comment(by kcrisman):
Replying to [comment:111 jpflori]:
> Replying to [comment:110 kcrisman]:
>
> > Another minor issue with the doctests. Am I correct that `maxima`
still gives the pexpect interface, while all 'calculus' stuff is done with
the library interface? In that case the stuff about calculus at the top
of `maxima.py` needs to be deleted, probably - perhaps put at the top of
`maxima_lib.py`, since we would want to keep the doctests and information?
> You're right about maxima and calculus, I'll have a look at that while
working on doctests.
>
Never mind, this is all correct as it stands. I have been singularly
unhelpful, though not by design. Maybe one could copy the material at the
top of `maxima.py` and put it in `maxima_lib.py` with a `from
sage.interface.maxima_lib import maxima` at the very beginning, with some
clarifying words. That would provide a double check, too.
There are also a few places in a few docs that still mention expect
wrongly, I think - I'll keep looking for them.
Issues I think I can deal with while taking care of the error handling:
* `maxima._expect_expr`, while usefully staying the same as before,
certainly isn't doctested by those tests any more.
* Can the old `sr_integral` etc. in `maxima.py` be removed, or should
they be kept in case someone wanted to use the pexpect for doing calculus?
I would think remove.
* With respect to `sr_sum` and `sr_integral`, since they are implementing
the divergent integral/sum check, should we remove those from
`calculus.py` and `symbolic.integration.external.py`? Those pieces of
code will probably never be reached, since the !ValueError is already
raised in `maxima_lib.py`.
I'll keep looking for things like this, hopefully catch as many as
possible.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7377#comment:112>
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.
