#16439: Allow inverse trig functions to all take complex input
-------------------------------------+-------------------------------------
Reporter: kcrisman | Owner:
Type: defect | Status: needs_review
Priority: minor | Milestone: sage-6.3
Component: symbolics | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/ppurka/allow_inverse_trig_functions_to_all_take_complex_input|
e776b188e54d567b2112aadb7cd8e13e6e6cbe59
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
Just one point - almost certainly some of those digits are 'extra' from
Python. Compare (after this):
{{{
sage: sec(1.+i)
0.498337030555187 + 0.591083841721045*I
sage: sec(complex(1,1))
(0.49833703055518686+0.5910838417210451j)
sage: sec(CDF(complex(1,1)))
0.498337030555 + 0.591083841721*I
}}}
Interesting.
Here is something else I don't know what to do with.
{{{
sage: arccot(1.+i)
arccot(1.00000000000000 + 1.00000000000000*I) # in SR
sage: cot(1.+i)
0.217621561854403 - 0.868014142895925*I
}}}
One would think this should be the same type of output.
That said, `SR` is useful for some other cases of exact input.
I'm wondering whether we want to try to fix all of this here, though.
--
Ticket URL: <http://trac.sagemath.org/ticket/16439#comment:13>
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.
