#4102: make bessel_J symbolic
----------------------------------+-----------------------------------------
Reporter: jwmerrill | Owner: burcin
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-5.11
Component: calculus | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: Karl-Dieter Crisman
Authors: Benjamin Jones | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by benjaminfjones):
When a symbolic function is lazily imported, its constructor isn't called
until the function is referenced and the constructor is responsible for
populating the symbol tables that make conversion work (e.g. maxima <->
sage). So with lazy importing here, if I start up Sage and call `desolve`
with Bessel's diffeq, we don't properly convert the result from Maxima to
Sage because the Bessel functions are not in the symbol table (they
haven't been constructed yet).
Any thoughts on this?
One idea I had is that we can register the conversions somewhere else (not
in the constructors). But that would mean maintaining each symbolic
function's code and its conversions in separate places (seems like a bad
idea).
Another idea: import from sage.functions.bessel strictly (i.e. not
lazily), but in bessel.py use lazy imports for everything that's not
needed in the constructors.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4102#comment:63>
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.
