I fully agree with your analysis. But still the result is wrong. Should I
file a bug? Is it a bug in Sage or in Numpy? I have no idea how the two
work together. I'd appreciate any hint on how to proceed.
Thanks,
Bernhard
On Friday, January 3, 2014 4:13:02 AM UTC+1, Harald Schilly wrote:
>
>
>
> On Thursday, January 2, 2014 9:22:14 PM UTC+1, [email protected] wrote:
>>
>> What's going on here?
>>
>
> These are two different "sqrt": the first one is a sage specific function,
> the second one is from numpy. it's just that numpy's sqrt(2) produces
> something (a float64 type) which makes troubles with the part from sage
> (which is not of type "complex", but
> "sage.rings.complex_number.ComplexNumber")
>
> here is a more isolated example:
>
> import numpy as np
> 1j / np.float64(2)
>
> which gives 0.
>
> note:
>
> type(1j)
> <type 'sage.rings.complex_number.ComplexNumber'>
>
> Harald
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-support" 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-support.
For more options, visit https://groups.google.com/groups/opt_out.
