#17130: Coercion after _eval_() in symbolic functions
-----------------------------+------------------------
Reporter: jdemeyer | Owner:
Type: defect | 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: | Stopgaps:
-----------------------------+------------------------
Comment (by jdemeyer):
Replying to [comment:8 kcrisman]:
> Perhaps one could take the coercion mutual parents of all args instead
for a minimal change?
That still wouldn't fix the case where the function is computed to less
precision than the inputs.
I think the following would fix most issues:
- before calling the function, convert all Python types to the
corresponding Sage types (`float` -> `RDF` and so on)
- after calling the function, convert back if needed
--
Ticket URL: <http://trac.sagemath.org/ticket/17130#comment:10>
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.
