#15200: _evalf_ handling of backends
-------------------------------+------------------------
Reporter: eviatarbach | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.4
Component: symbolics | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: #12289 | Stopgaps:
-------------------------------+------------------------
Comment (by jdemeyer):
I think the best solution would be to hardcode a set of common
algorithm/parent choices like:
{{{
#!python
def _evalf_(self, *args, parent=None, algorithm=None):
if hasattr(self, '_evalf_scipy_') and
(some_condition_on_parent_and_algorithm):
return parent(self._evalf_scipy_(*args))
if hasattr(self, '_evalf_mpmath_') and
(some_condition_on_parent_and_algorithm):
return parent(self._evalf_mpmath_(*args))
[...]
return self._evalf_default_(*args, parent=parent, algorithm=algorithm)
}}}
--
Ticket URL: <http://trac.sagemath.org/ticket/15200#comment:7>
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.
