#14766: Fix Python int problem with exp_integral
-----------------------------+-------------------------
Reporter: kcrisman | Owner: burcin
Type: defect | Status: new
Priority: major | Milestone: sage-5.12
Component: symbolics | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-----------------------------+-------------------------
Changes (by eviatarbach):
* cc: eviatarbach (added)
Comment:
I'm guessing this occurs in other files too.
I think it's unreasonable to expect everyone adding symbolic functions to
worry about this, and certainly users to be aware of it; maybe we could
make `BuiltinFunction.__call__` automatically convert `int` to `Integer`?
Or have it raise an error if an `int` is in the parameters? Allowing `int`
into `_eval_` causes other problems too, such as getting expressions with
`int` pyobjects in them, making arithmetic slower, etc.
At the very least, we could temporarily add `from __future__ import
division` in all files that implement symbolic functions; then exact
answers wouldn't be returned in all cases where they should, but at least
mathematically wrong answers wouldn't occur.
--
Ticket URL: <http://trac.sagemath.org/ticket/14766#comment:3>
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.
