#14743: SymbolicFunction gives errors when using unbounded methods
-------------------------------------+--------------------------------------
Reporter: nvcleemp | Owner: burcin
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.11
Component: symbolics | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Nico Van Cleemput | Merged in:
Dependencies: | Stopgaps:
-------------------------------------+--------------------------------------
Comment (by nbruin):
I suspect that if people try to define a symbolic function that gets
evaluated via an unbound method, they are doing the wrong thing: An
unbound method expects a "self" argument and expects that to be of a very
particular type (and usually not a "symbolic expression"). Symbolic
functions, on the other hand only get symbolic expressions as arguments,
and need to be extremely tolerant (or at least careful) in handling the
different types of objects that might come wrapped in such a package.
Symbolic functions are only for calculus-type applications. For most other
situations one should use python functions/methods straight away.
I would say that the proper fix is to check that the documentation
contains information along these lines, not to make it easier to use the
wrong tool for the job.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14743#comment:4>
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/groups/opt_out.
