#15695: Coercion problems between numpy and sage floats
-------------------------------------+-------------------------------------
Reporter: nbruin | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.4
Component: coercion | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/nbruin/ticket/15695 | f07008bd6f1e9b5a37a4d3eae874a5eac2815234
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
Hello,
I propose to close this as duplicates because of #18076. With the branch
applied
{{{
sage: import numpy
sage: 1j + numpy.float64(2)
2.00000000000000 + 1.00000000000000*I
sage: parent(_)
Complex Field with 53 bits of precision
}}}
But #8824 is still an issue
{{{
sage: numpy.float64(2) + 1j
(2+1j)
sage: parent(_)
<type 'numpy.complex128'>
}}}
Since as I copied some of the suggestions from the branch, I propose to
set you as an author in #18076.
Vincent
--
Ticket URL: <http://trac.sagemath.org/ticket/15695#comment:7>
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.
